Feature: Temporary exemptions

Open
#58 2 comments 0 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
Needs clarification
Activity status
Quiet
Tech stack
github-actions, python
Domain
devops, tooling

Research direction

Start by reading the stale-repository detection flow and the GitHub Action configuration, since the issue names no files or tests. Define how a repository records its last activity confirmation, how the X-month period is configured, and what replaces the public keep tag before adding coverage for the full lifecycle.

Written by the indexing model from the issue text.

Description

enhancement good first issue keep

Would it make sense to track on what date someone confirmed the repository was still active, and that way you could confirm that was still the case after X months? As a bonus, we won't have a mysterious, public, keep tag on several of our repositories!

Dominant language
Python
Stars
205
Forks
36
Avg merge
11h 45m
Merged PRs (30d)
8

Getting set up

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.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.