Share timestamp between workflow steps#13
Conversation
…n steps Co-authored-by: hesreallyhim <172150522+hesreallyhim@users.noreply.github.com>
|
@copilot You must also update the "Last issue created at" timestamp with the new timestamp |
The "Update Issue created-at time" step already updates the "Last Issue created at:" timestamp in the baseline section (line 45 of the workflow): sed -i 's/Last Issue created at: `[^`]*`/Last Issue created at: `'"$TIMESTAMP"'`/g' README.mdThis replaces the PLACEHOLDER with the current timestamp, and that same timestamp is then reused in the "Update nonce" step for the "Last updated:" field. Both timestamps will be identical as requested in the original issue. (commit c8cbd8e) |
|
@copilot and then will both timestamps get update each time the workflow runs |
Yes, both timestamps will be updated each time the workflow runs (when an issue with "nonce" in the body is opened). They will both show the identical timestamp value because:
Each workflow run generates a new timestamp that replaces both fields simultaneously. |
Complete the "Update Issue created-at time" step to update the README's PLACEHOLDER timestamp and share that value with the "Update nonce" step so both use identical timestamps.
Changes:
id: update-timestampandGITHUB_OUTPUTto capture timestamp for reuseLast Issue created at: PLACEHOLDERpatternOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.