Drone CI Suport (reference)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Continuous integration is a very important feature nowadays. It has existed for many years with Jenkins as the benchmark in the market.
I started a discussion about supporting "Keybase Git" with Drone CI in the link:
https://github.com/drone/drone/issues/2254#issuecomment-343528520
It's just a discussion that I'm willing to participate in by giving validating and testing support - Because my level is intermediate and operational. I know the Git feature is new to Keybase, but it would be nice to have this third-party support on the Roadmap.
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 reviewing the linked Drone CI discussion in drone/drone#2254 and the Keybase Git context described here. No files, tests, or implementation entry points are named; done would require an agreed support scope or roadmap decision for Drone CI integration, with validation and testing expectations documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100