Where do I go to report an issue?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
We have myriad gitlab projects to track issues.
Where do I go when I have an issue for something?
Cheaha Software: https://gitlab.rc.uab.edu/rc/cluster-software/-/issues
General devops issues: https://gitlab.rc.uab.edu/rc/devops/-/issues
Researcher-facing Documentation: https://github.com/uabrc/uabrc.github.io/issues
Others forthcoming...
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 documentation structure and the three issue destinations listed in the message. Determine where issue-reporting guidance belongs and whether the listed projects and links are current. Done means contributors can identify the correct destination for software, DevOps, and researcher-facing documentation issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100