Swap required CI checks in the master ruleset when distribution merges to master

Open
  • Is something wrong?
#155 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
18/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
ansible, github-actions, python
Domain
ci-cd

Research direction

At the distribution-to-master merge, open Settings → Rules → Rulesets and select the master ruleset. Replace the required Local tests check with Syntax, CLI tests, Ansible tests, and Unit tests, keeping the up-to-date requirement unchanged. Done when PRs into master require all four checks and no longer require Local tests.

Written by the indexing model from the issue text.

Description

One-time repo setting to change when distribution is merged into master.

#154 (for #151) split PR CI into four jobs. The repository ruleset master (Settings → Rules → Rulesets, target: default branch) still requires the old status check Local tests, which no longer exists on distribution.

When

In the same step as the distribution → master merge. Not earlier: until that merge, master's workflow only reports Local tests, so swapping now blocks every PR into master. Not later: after the merge, Local tests never reports and every PR into master is blocked.

What

In ruleset master → Require status checks to pass, remove Local tests and add:

  • Syntax
  • CLI tests
  • Ansible tests
  • Unit tests

(shown in the PR checks UI as CI / Syntax, and so on). Keep "Require branches to be up to date" as it is.

Done when

A PR into master shows the four checks as required and Local tests is gone.

Dominant language
Python
Stars
138
Forks
51
Avg merge
1h 38m
Merged PRs (30d)
48

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from splunk/splunk-platform-automator

All issues in splunk/splunk-platform-automator

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.