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

Also run CI an the main/master branch #864

Merged
merged 2 commits into from
Jan 22, 2024
Merged

Commits on Jan 9, 2024

  1. Also run CI an the main/master branch

    When merging a passing PR which was not on top of the last commit of the
    main branch, we may break CI.  This make sure a CI run is triggered when
    the main branch is updated.  As GitHub kindly display the status of the
    last commit on a project page, this allow to quickly see if a module CI
    works as intended or not.
    
    The main branch of most of our modules is `master` but a few use the
    more inclusive `main` name, so enable ci for both.
    smortex committed Jan 9, 2024
    Configuration menu
    Copy the full SHA
    2195a16 View commit details
    Browse the repository at this point in the history

Commits on Jan 22, 2024

  1. Make the main branches tunable

    Some consumers of modulesync want to enable this for e.g. a `develop`
    branch, so make it tunable and use the `main` and `master` names as
    default value for this new setting which should work out-of the box for
    most cases.
    smortex committed Jan 22, 2024
    Configuration menu
    Copy the full SHA
    28a40a6 View commit details
    Browse the repository at this point in the history