Remove 'Last revised' line from acknowledgements #435
Merged
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
It complicates the generation of acknowledgements and can lead to changes in the git history where only that value is updated and that are therefore mainly noise without real benefit. Because the acknowledgements are now generated and updated regularly and automatically as part of the release process, the value of that field is in general questionable. To keep the workflow simpler respectively to not complicate it more in order to avoid updates of only this field, it's just removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It complicates the generation of acknowledgements and can lead to changes in the git history where only that value is updated and that are therefore mainly noise without real benefit.
Because the acknowledgements are now generated and updated regularly and automatically as part of the release process, the value of that field is in general questionable.
To keep the workflow simpler respectively to not complicate it more in order to avoid updates of only this field, it's just removed.
See remarks in