feat: add opt-in --preserve-generated-from option #940
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
3 tasks
Codecov Report
@@ Coverage Diff @@
## main #940 +/- ##
==========================================
+ Coverage 93.34% 93.46% +0.11%
==========================================
Files 90 91 +1
Lines 4809 4850 +41
Branches 401 405 +4
==========================================
+ Hits 4489 4533 +44
+ Misses 319 316 -3
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
🎉 This is included in version v1.35.0 🎉 The release is available on: Cheers! 📦🚀 |
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.
PR Checklist
status: accepting prsOverview
GitHub doesn't have a unified "create a new blank repository" API. So unless the new
--preserve-generated-fromoption is true, repo creation will check whether the authenticated user has the same login as the--owneroption, then use eithercreateForAuthenticatedUseror `createInOrg.Slightly rephrases the end-of-README notice while I'm here to remove my username from it. And in doing so, expands the "does the notice already exist?" logic to check previous variants.