github / github/branch-deploy

Support For Granular Locking Mechanisms.

Offen
#438 5 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
question
Vorherrschende Sprache
TypeScript
Sterne
576
Forks
74
Ø Merge
11 Std. 7 Min.
Gemergte PRs (30 T.)
1

Beschreibung

### Details

First of all, we really thank you for this project. It's really one of my favorite GHA related projects.

## The Problem
We recently realized that sticky locks lock on a user level, not on a PR level.
This recently caused a problem for us because one of our developers forgot to merge and deployed another PR, effectively rolling back the changes of his previous PR.

## The Suggestion
We would like it if locks could also work on a PR or Branch basis.

---

I would be glad to contribute if that's ok, but I wanted to check if my assumption and suggestion was valid first.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

No files, tests, or entry points are named. Start by locating the existing sticky-lock handling and deployment workflow, then clarify whether locks should be scoped to pull requests, branches, or both. Done should include the agreed granular behavior and coverage for the relevant locking cases.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github-actions, typescript
Bereich
ci-cd, devops
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.