Guidelines on how to contribute
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 306
- Forks
- 119
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
Hi everyone. We would like to start contributing to HeCBench with fixes and potentially more, if there is an appetite for it.
We have a few questions on how to contribute best:
- Should we file issues and then PRs to address those issues?
- Should we just open PRs with fixes, or should we open issues and then PRs?
- Is there a policy around AI-assisted contributions (human-reviewed before PRs)?
Thanks for your answers.
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 with the three contribution-policy questions listed in the issue; no files, tests, or entry points are identified. Done means the project has settled, discoverable answers about issue and PR workflow and AI-assisted contributions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100