Different label based on new/changed/removed

Open

#47 opened on Jan 20, 2020 5 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: github-actions, typescript, yaml
Domain: ci-cd, tooling

Research direction

Review the YAML configuration examples in the issue and compare them with the linked ericcornelissen/labeler prototype and its example PRs. Define how added, modified, and removed files should map to labels, including combined and unrestricted patterns; done means pull requests receive the expected labels for each change type.

Written by the indexing model from the issue text.

Description

feature request needs eyes

I was wondering if it is either possible or desired to have a feature to: configure a label based on whether a file was newly created vs. a file was changed (vs. a file was removed).

In configuration I would imagine this could be written as follows:

"label on add":
  - on: added
  - example/**/*

"label on change":
  - on: modified
  - example/**/*

"label on remove":
  - on: removed
  - example/**/*

"label on multiple":
  - on:
    - added
    - modified
    - removed
  - example/**/*

"or if you don't care":
  - example/**/*

"and even": example/**/*

I have a working prototype at ericcornelissen/labeler (example PR added, example PR modified) which I could turn into a Pull Request for this project if there is more interest in this 😄

In practice I want to use this in simple-icons/simple-icons to label Pull Requests with either new icon or icon outdated based on whether a new icon was added or an icon was updated (respectively)

Dominant language: TypeScript
Stars: 2.5k
Forks: 492
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

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

Similar issues

[Bug]: Session row status indicator sits flush against the selection pill's rounded corner Open

clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#154145 · 2 comments · 1 reaction · Opened Sep 20, 2026
[good first issue] 🀄 Add new Grammar Point 265 (good-first-issue) Open

community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs

Difficulty 1/5 Under an hour Newbie friendliness 76/100

lingdojo/kana-dojo#30632 · 1 comment · 5 reactions · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026
`QuotedTweet.self_thread` is optional in syndication responses Open

Difficulty 1/5 Under an hour Newbie friendliness 88/100

vercel/react-tweet#225 · Opened Sep 20, 2026

More TypeScript issues