redhat-developer / redhat-developer/app-services-sdk-go
Create tests based on examples that will help us to setup proper conventional commits when merging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 16
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 4
Description
If our API dosn't compile or lint after generation we should change tests and create BREAKING commit/changelog.
Otherwise we might create fix or feature depending on original commit that came from the source repo.
Getting information about commit or PR of the source repository will be additionally very useful when dealing with this problems
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
Start with the API generation workflow and its compile and lint checks, then review how merges currently determine conventional commit types and changelogs. Add tests based on the stated examples so generated API failures produce breaking changes, while other cases retain the appropriate fix or feature classification; verify source repository commit or pull request metadata is handled if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, release, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100