improve names of CI checks and do not run them on merges to master #6089
Conversation
not convinced it is needed to run the checks after a merge to master branch in addition to running them before merging a PR Signed-off-by: Matthieu Gallien <[email protected]>
mgallien
force-pushed
the
ci/betterNamesForCiChecks
branch
from
0cda523 to
bb09bc6
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
|
AppImage file: nextcloud-PR-6089-bb09bc67fc94080f6412491bc7f6a863d37d096a-x86_64.AppImage |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #6089 +/- ##
=========================================
Coverage ? 60.33%
=========================================
Files ? 145
Lines ? 18800
Branches ? 0
=========================================
Hits ? 11343
Misses ? 7457
Partials ? 0 |
|
/backport to stable-3.10 |
|
The backport to stable-3.10 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable-3.10
git pull origin stable-3.10
# Create the new backport branch
git checkout -b fix/foo-stable-3.10
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable-3.10More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
not convinced it is needed to run the checks after a merge to master branch in addition to running them before merging a PR