Skip to content

Commit

Permalink
CI: run msync with branch foobranch
Browse files Browse the repository at this point in the history
By default we write into the branch modulesync. That's configured in
modulesync.yml. msync will check for an existing branch and then update
it, instead of master. That's fine for normal operations, but not for
our CI. Our noop run in CI should detect which modulesync_config changes
aren't yet merged, so we need to use a different branch here.
  • Loading branch information
bastelfreak committed Jan 14, 2024
1 parent 2ac21be commit 60dcef3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ jobs:
ruby-version: 2.7
bundler-cache: true
- name: Run msync --noop
run: bundle exec msync update --noop --git-base=https://github.com/
run: bundle exec msync update --noop --git-base=https://github.com/ --branch foobranch
metadata_json_deps:
runs-on: ubuntu-latest
name: Run metadata_json_deps on all modules
Expand Down

0 comments on commit 60dcef3

Please sign in to comment.