Skip to content
Snippets Groups Projects

Don't run the downtime check on stable branches, or tags/master

Merged DJ Mountney requested to merge no-downtime-check-stable into master

What does this MR do?

Ignores the downtime check for stable branches

Why was this MR needed?

The way the check currently works, it runs on the diff between your branch and the latest commit in gitlab on master.

This doesn't give a good representation of the changes migrations for stable branches, tags, and master itself.

And is currently causing failures in the 9.0 branch

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
Please register or sign in to reply
Loading