Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create a separate CI workflow for staging-blast branch #328

Closed
smol-ninja opened this issue Apr 12, 2024 · 1 comment
Closed

Create a separate CI workflow for staging-blast branch #328

smol-ninja opened this issue Apr 12, 2024 · 1 comment
Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: ci Changes to our CI configuration files and scripts. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@smol-ninja
Copy link
Member

Since staging-blast branch contains 1 additional commit on top of the staging branch, a separate CI workflow should be added to the staging-blast branch that runs automatically everytime staging-blast branch is updated.
@smol-ninja smol-ninja added priority: 1 This is important. It should be dealt with shortly. effort: medium Default level of effort. type: ci Changes to our CI configuration files and scripts. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. labels Apr 12, 2024
@smol-ninja
Copy link
Member Author

Resolved in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: ci Changes to our CI configuration files and scripts. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smol-ninja