Update push settings #35
Merged
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
mmlb
force-pushed
the
update-drone-push-settings
branch
2 times, most recently
from
5f7b533 to
0c890f9
Compare
PRs should go to tink-pr using PULL_REQUEST instead of BRANCH because most PRs will (hopefully ;) ) come in from forks.
mmlb
force-pushed
the
update-drone-push-settings
branch
5 times, most recently
from
230e716 to
85fed86
Compare
So we build all the binaries.
We build outside of the Dockerfile in CI.
mmlb
force-pushed
the
update-drone-push-settings
branch
from
85fed86 to
6bfc75d
Compare
mmlb
force-pushed
the
update-drone-push-settings
branch
from
6bfc75d to
414b3ea
Compare
nathangoulding
approved these changes
Apr 2, 2020
Cbkhare
added a commit
to Cbkhare/tink
that referenced
this pull request
Jul 1, 2020
gauravgahlot
pushed a commit
that referenced
this pull request
Jul 6, 2020
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.
PRs should go to tink-pr using PULL_REQUEST instead of BRANCH because most PRs will (hopefully ;) ) come in from forks.