NO-ISSUE: Update NOTICE Copyright year automatically on 1th of January #2788
Conversation
This file contains 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
|
All PRs will become red on January 1st if we merge this, won't they? 🙈 |
jomarko
changed the title
|
@tiagobento thank you for the feedback, I changed the solution. It should open PR with needed update don the first of january. Please let me know your opinion. Or please propose what should be the solution. I will then adapt PRs for other repositories. |
|
The team conclusion is we will not merge this: The use a 3rd party GitHub Action is not allowed by Apache. Also automation of simple update, that is needed once a year is not worth, probably. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The added action should open a pull request on 1th of January and update the NOTICE Copyright year to be up to date.