Drop tito as a dependency
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 13
- Avg merge
- 1h 13m
- Merged PRs (30d)
- 1
Description
Tito serves as middleman for operations to Koji. Projects can end up duplicating information in tito configuration that is present in the package manifest. This issue aims to replace all the functionality tito handled with native functionality to drop tito and drive all configuration through the package manifest as the source of truth.
Target items:
- Running Koji commands directly to perform scratch builds
- Running Koji commands directly to perform releases
- Handling dist-git commit
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the Tito integration, the package manifest, and the code handling Koji operations. Map how scratch builds, releases, and dist-git commits currently work, then verify that the package manifest is the sole configuration source and Tito is no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100