[codex] Fix release-hold auth and timestamp parsing#10
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
GH_TOKENto the composite step soghcommands authenticate in GitHub Actionsdate -dtimestamp parsing with a portable Python-based ISO-8601 conversionWhy
The new
release-holdaction had two portability issues:ghwas invoked without an auth token, which can fail in CI and private repositoriesdate -donly works on GNU date, so the action would fail on macOS runnersImpact
release-holdnow works with authenticatedghcalls by default in GitHub ActionsValidation
release-hold/action.ymlsuccessfully with Ruby YAML