Publish pre-release OCK #270
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
Apparently 403 error occurs when you don't have enough permissions. I am guessing the code is fine, just need permissions to make sure I can actually create releases, or someone who has permissions can try my code. |
MaryaSharf
force-pushed
the
marya/publish
branch
from
b11a912 to
df180f2
Compare
|
Created a personal token but that need to be added to the repository secret in settings, which I dont have access to. |
MaryaSharf
force-pushed
the
marya/publish
branch
from
48a37fb to
2409433
Compare
coldav
reviewed
Jan 9, 2024
MaryaSharf
force-pushed
the
marya/publish
branch
4 times, most recently
from
3259478 to
c8c3543
Compare
every push to stable branch.
MaryaSharf
force-pushed
the
marya/publish
branch
from
4579936 to
e19d2b3
Compare
coldav
approved these changes
Jan 12, 2024
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.
Overview
Create a pre-release version of OCK on github stable branch on every new push.
Description of change
Every time there's a new push to the stable branch, this workflow will be triggered and will create
a new OCK release on github.
It uses GITHUB_TOKEN, which has been added to the repository secrets and also uploaded on 1password.