devicons/devicon

Add a `do not merge` label that prevents merging

Open

#1,684 opened on Feb 18, 2023

View on GitHub
 (3 comments) (1 reaction) (0 assignees)CSS (2,448 forks)batch import
devopsgood first issue

Repository metrics

Stars
 (11,625 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Discussed in https://github.com/devicons/devicon/discussions/1429

Originally posted by Snailedlt October 4, 2022 Would it be useful to have a do not merge label? Maybe the PR could have a job that fails if the label is applied too.

Example implementation from here: https://www.jessesquires.com/blog/2021/08/24/useful-label-based-github-actions-workflows/#updated-21-march-2022

name: Do Not Merge

on:
  pull_request:
    types: [synchronize, opened, reopened, labeled, unlabeled]

jobs:
  do-not-merge:
    if: ${{ contains(github.event.*.labels.*.name, 'do not merge') }}
    name: Prevent Merging
    runs-on: ubuntu-latest
    steps:
      - name: Check for label
        run: |
          echo "Pull request is labeled as 'do not merge'"
          echo "This workflow fails so that the pull request cannot be merged"
          exit 1

Contributor guide

Research direction
Create a GitHub Action workflow file and add a 'do not merge' label to the repository. The workflow should fail if the label is applied.
Tech stack
github actions
Domain
devopsci cdtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80