-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(github-action): retain spaces in extracted values #32730
feat(github-action): retain spaces in extracted values #32730
Conversation
This update ensures that Renovate retains the number of whitespaces already present in the GitHub Action YAML file. If there are no existing comments indicating the version number (e.g., when initially pinning a dependency), Renovate's behaviour remains unchanged (that is, it will insert a single space between the commit hash and the `#`). Signed-off-by: JP-Ellis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise LGTM
Co-authored-by: Michael Kriese <[email protected]>
Awesome thanks! All changes incorporated 🚀 |
I see there's a lint issue in CI about a missing comma in the |
Interestingly it needed a |
Oh wow, I'm surprised vscode didn't highlight the issue 🤔 Thanks though! |
🎉 This PR is included in version 39.38.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…2730) Signed-off-by: JP-Ellis <[email protected]> Co-authored-by: Michael Kriese <[email protected]> Co-authored-by: Rhys Arkins <[email protected]>
Changes
This update ensures that Renovate retains the number of whitespaces already present in the GitHub Action YAML file.
If there are no existing comments indicating the version number (e.g., when initially pinning a dependency), Renovate's behaviour remains unchanged (that is, it will insert a single space between the commit hash and the
#
).Context
Documentation (please check one with an [x])
Note
I do not believe this requires a documentation update as it is a rather transparent feature, but please let me know otherwise.
The GitHub Actions docs do contain a link to the above ticket that will be closed.
How I've tested my work (please select one)
I have verified these changes via: