feat: add --skip-remote-check option #2426
Draft
+87
−41
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
This new option will bypass checking remote access. It only works in dry run mode. This addresses semantic-release#2232.
Pinappleplayer
approved these changes
May 2, 2022
|
Any movement on this? I would love to see this come to fruition. |
|
This would also help my current issue! |
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.
This is a first draft of a new option to bypass checking remote access. It only works in dry run mode. There is still some work that needs to be done before it's ready to merge:
runthrow instead of returningfalse? (index.js#63)I took a first stab at writing some tests for this new flag, but I got lost in the tests and couldn't figure out how to make some of them work. If someone with more experience in this test suite could help out that would be greatly appreciated.
Once this is ready I will opened corresponding PRs on @semantic-release/github and @semantic-release/npm to use this option.
Closes #2232.