Notify PR authors about repository migration - #6611
Merged
Merged
Conversation
Related example: #6603
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
Thanks for contributing to the ClickHouse documentation! We’ve moved documentation development to the main ClickHouse/ClickHouse repository. For future documentation changes, please open your pull request there, with changes under the docs/ directory. We’ll continue reviewing this pull request here during the transition, and it will be transferred as part of the migration. You don’t need to reopen it. See the documentation README for more information. |
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
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.
Summary
Mention the pull request author in the automated repository migration notice so GitHub sends an explicit mention notification and the notice is harder to overlook.
This follows the existing automated author-mention pattern in the trademark license agreement workflow.
Related: #6603
Checklist