You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
Each file that is updated by release-please has it's own commit. This is presumably because it is using the Contents API.
For example, the Contents API generates a git commit for each addition or change and uses the current time as the timestamp.
When one or two files are updated, this isn't as much of an issue, however, this is less than ideal once more files are updated (e.g. the addition of package-lock.json with #464).
Describe the solution you'd like
Ideally, all the updates related to the version number bump would be applied in a single commit. It looks like this could technically be achieved by using the Commits API.
Using the Commits API looks more complicated than the Contents API so I can understand if you don't think the increase in complexity is unjustified.
Describe alternatives you've considered
The alternative is to continue with individual commits and remember to merge the release pull request with the squash and merge option.
Additional context
Example of commits with three changes
The text was updated successfully, but these errors were encountered:
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
Each file that is updated by
release-please
has it's own commit. This is presumably because it is using the Contents API.When one or two files are updated, this isn't as much of an issue, however, this is less than ideal once more files are updated (e.g. the addition of
package-lock.json
with #464).Describe the solution you'd like
Ideally, all the updates related to the version number bump would be applied in a single commit. It looks like this could technically be achieved by using the Commits API.
Using the Commits API looks more complicated than the Contents API so I can understand if you don't think the increase in complexity is unjustified.
Describe alternatives you've considered
The alternative is to continue with individual commits and remember to merge the release pull request with the squash and merge option.
Additional context
Example of commits with three changes
The text was updated successfully, but these errors were encountered: