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

feat: update extra-files based on the commit sha #2444

Open
dsotirakis opened this issue Dec 3, 2024 · 0 comments
Open

feat: update extra-files based on the commit sha #2444

dsotirakis opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@dsotirakis
Copy link
Contributor

Is your feature request related to a problem? Please describe.

While working on trying to update README file references after every version update, I thought that it'd be better if the sha was also updated along with the version, since this a really common pattern for GitHub Actions.

Another reason is automated updates (renovate, dependabot) where they most likely waiting for sha updates, rather than semver.

Describe the solution you'd like

Be able to get automated README updates using release-please, so the users of the workflow will now every time which is the latest version/sha of an action.

Describe alternatives you've considered

Create a custom action outside of release please to do this. While this may also be a viable solution, it was pretty obvious to me that going with sha updates would be something that other users would like as well to be included in release-please.

@dsotirakis dsotirakis added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants