Call-for-Code-for-Racial-Justice / Call-for-Code-for-Racial-Justice/Hacktoberfest
Find and Fix Bugs | Start here
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 2
- Forks
- 1
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
## Background
This issue provides directions on how you can contribute to one of our Call for Code for Racial Justice repositories by documenting bugs and fixing them. Please keep this issue open.
## Tasks
- [ ] Check out the open issues, ensure you're not replicating existing issues
- [ ] Read & follow the instructions in the Getting Started Section of the project of your choice, [find all projects here](https://call-for-code-for-racial-justice.github.io/Hacktoberfest/#/projects/legit-info).
As you run across any bugs (error messages, etc)
- [ ] if your issue is more of a suggestion for improving the UI go to this issue instead
- [ ] create a new issue using the bug template
- [ ] label it `hacktoberfest` `bug`
- [ ] Discuss the bug you found in the issue, maintainers of the project will also comment on your issue.
If you are able to fix the bug
- [ ] comment in the issue to claim the issue
- [ ] add details on your proposed fix to the issue
- [ ] Discuss the issue maintainers of the project will also comment on your issue.
- [ ] Fork the repository.
- [ ] Commit your changes to your fork & submit your pull request
- [ ] Handle any feedback before the request is merged.
- [ ] PR merged by team
- [ ] Congratulations!
If you are unfamilar with pull requests, committing code on Github, we recommend you check out our free course on open source: [ibm.biz/opensourcecourse](ibm.biz/opensourcecourse)
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par la section Getting Started accessible depuis le répertoire des projets à l’adresse https://call-for-code-for-racial-justice.github.io/Hacktoberfest/#/projects/legit-info, puis choisissez un repository et examinez ses issues ouvertes avant de le tester. La tâche est terminée lorsque vous documentez un bug reproductible dans une nouvelle issue ou soumettez une pull request qui le corrige après discussion avec les maintainers.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- documentation
- Type d'issue
- Documentation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 20/100