Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update release instructions based on 1.20.5 release #14239

Merged

Conversation

dsherret
Copy link
Member

@dsherret dsherret commented Apr 8, 2022

Some issues I found along the way. Slowly getting there.

git config user.email "${{ github.actor }}@users.noreply.github.com"
git config user.name "${{ github.actor }}"
git config user.email "propelml@gmail.com"
git config user.name "denobot"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it would be cuter if denobot bumps the versions.

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# the default secrets.GITHUB_TOKEN won't trigger a workflow run
# when tagging, but it will if we provide a custom PAT
GITHUB_TOKEN: ${{ secrets.DENOBOT_PAT }}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See https://github.community/t/pushing-a-tag-within-an-action-doesnt-trigger-another-workflow/201080/5

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dsherret dsherret merged commit a4eee00 into denoland:main Apr 8, 2022
@dsherret dsherret deleted the chore_update_release_instructions_deno_std branch April 8, 2022 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants