microsoft / microsoft/finops-toolkit

GitHub action to block PRs into main

Open
#200 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help wanted ✨ Skill: DevOps
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

⚠️ Problem

All PRs should be submitted against dev, but GitHub doesn't support that as a default PR branch when the code needs to show main for the latest stable release.

🛠️ Solution

Add a GitHub action that blocks PRs main and creates a new one against dev.

ℹ️ Additional context

We should also consider switching the default branch to dev and moving documentation out to a separate site. That would minimize the issue, but we still need to block PRs to main.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the repository's GitHub Actions configuration and how pull requests target the main and dev branches. Define the action's behavior for pull requests opened against main, including how a replacement request against dev should be created, then verify the workflow with representative pull requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.