Remove overriding header while pushing deployment scripts #815
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
Signed-off-by: Christian Wolf <[email protected]>
Signed-off-by: Christian Wolf <[email protected]>
christianlupus
force-pushed
the
fix/800-no-push-possible
branch
from
8bcb601 to
3a724d4
Compare
Signed-off-by: Christian Wolf <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #815 +/- ##
=======================================
Coverage 21.40% 21.40%
=======================================
Files 20 20
Lines 1542 1542
=======================================
Hits 330 330
Misses 1212 1212
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Currently, the deployment scripts are non-functional as the authorization header is set in the config file and overrides the authorization parameters in the URL. Thus, the authorization headers must be cleared for successfully pushing using a PAT.