googleapis / googleapis/release-please
Different git forge providers possible?
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 588
- Avg merge
- 12h 16m
- Merged PRs (30d)
- 7
Description
As you probably have witnessed on your own GitHub slowely becomes an unreliable foundation for running Ci. (Evidence A: today's outage) As release please is my favourite pick for semantic commit releases I was wondering if it would be worth the effort to add a pr introducing forgejo/Gitea as a provider or if it's something you would categorically deny
Besides that, thank you for building and maintaining this piece of software
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing release-please's existing provider support and the Forgejo/Gitea integration requirements, then define the supported scope and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100