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.

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

[Chore] Run CI on 'main' and 'staging' #132

Merged
merged 1 commit into from
Sep 3, 2024
Merged

Conversation

rvem
Copy link
Member

@rvem rvem commented Sep 2, 2024

Description

Problem: Currently CI is only run on pull requests. However, there is a 'deploy' job that is supposed to be run on the 'staging' branch.

Solution: Run CI on pushes to 'main' and 'staging' branches.

Related issue(s)

Fixed #

✅ Checklist for your Pull Request

Related changes (conditional)

  • Tests

    • If I added new functionality, I added tests covering it.
    • If I fixed a bug, I added a regression test to prevent the bug from
      silently reappearing again.
  • Documentation

    • I checked whether I should update the docs and did so if necessary:

Stylistic guide (mandatory)

✓ Release Checklist

  • I updated the version number in package.yaml.
  • (After merging) I created a new entry in the releases page,
    with a summary of all user-facing changes.
    • I made sure a tag was created using the format vX.Y

@rvem rvem requested a review from Sereja313 September 2, 2024 09:40
Problem: Currently CI is only run on pull requests. However, there is a
'deploy' job that is supposed to be run on 'staging' branch.

Solution: Run CI on pushes to 'main' and 'staging' branches.
@rvem rvem force-pushed the rvem/run-ci-on-default-branch branch from 1c53aac to 4abade0 Compare September 2, 2024 09:40
@rvem rvem merged commit 028d9f1 into main Sep 3, 2024
4 checks passed
@rvem rvem deleted the rvem/run-ci-on-default-branch branch September 3, 2024 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants