Signify library vs application
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
It will probably be important to siginify in a repo if its a library or an application, since this impacts expectations on "downstream" (reverse) dependencies.
As an example, it makes sense to enable dependabot alerts to keep dependencies up to date with latest versions for applications, but to have libraries be more conservative in their requirements, since updating a requirement in a lib will require all consumers to also update.
Contributor 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.
Research direction
No file, test, or entry point is named in the issue. First determine how this repository should signify whether it is a library or an application, and how that distinction would affect dependency expectations. Done means the repository has an agreed, usable distinction that supports the stated Dependabot policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100