Run CI on main branch - Githubissues

agera-edc / MinimumViableDataspace

Guidance on documentation, scripts and integration steps on using the EDC project results

Apache License 2.0

0 stars 2 forks source link

Run CI on main branch #209

Closed algattik closed 2 years ago

algattik commented 2 years ago

What this PR changes/adds

Run CI (verification and test deployment) on merge to main branch.

Why it does that

Provide a baseline to verify that the CI on main branch is green.

Further notes

Linked Issue(s)

Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly?

cpeeyush commented 2 years ago

@algattik There also a trigger which is for when a PR gets merged https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-when-a-pull-request-merges-1.

I have never used it but just sharing it here.

ouphi commented 2 years ago

There is no corresponding story.

algattik commented 2 years ago

There is no corresponding story.

correct

algattik commented 2 years ago

@algattik There also a trigger which is for when a PR gets merged https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-when-a-pull-request-merges-1.

I have never used it but just sharing it here.

Thanks, interesting. Still, it makes sense for downstream projects to run the pipelines when they refresh main, so they can ensure they have a working base setup