FAILED: Repository Linter Issue: rl-repository_activity

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
devops

Research direction

Start by reviewing the default branch history to confirm whether any non-bot activity occurred within the last six months. Determine whether the repository should be archived or what concrete maintenance work would restore activity; done means the repository lifecycle decision is implemented and the rl-repository_activity check no longer reports a violation.

Written by the indexing model from the issue text.

Description

A violation against the SAP Open Source standards have been detected.

Rule: rl-repository_activity

Message: No activity by non-bot users in the default branch within the last 6 months. Inactive repositories should be archived.

Description: Checks if there has been activity by non-bot users in the default branch within the last 6 months. Repositories which are not archived should be actively used.

Documentation

Dominant language
No language data
Stars
100
Forks
41
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from SAP-samples/btp-developer-guide-cap

All issues in SAP-samples/btp-developer-guide-cap

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.