From 6375d0e2ff783dfebfe7711d3a1afad93285b963 Mon Sep 17 00:00:00 2001 From: Wodsfort Date: Sun, 13 Jul 2025 18:42:17 +0300 Subject: [PATCH 1/2] Add information about Gitlab Signed-off-by: Wodsfort --- _articles/how-to-contribute.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md index 774b3b63710..2965e78cf1b 100644 --- a/_articles/how-to-contribute.md +++ b/_articles/how-to-contribute.md @@ -181,7 +181,7 @@ A project also has documentation. These files are usually listed in the top leve Finally, open source projects use the following tools to organize discussion. Reading through the archives will give you a good picture of how the community thinks and works. * **Issue tracker:** Where people discuss issues related to the project. -* **Pull requests:** Where people discuss and review changes that are in progress, whether it's to improve a contributor's line of code, grammar usage, use of images, etc. Some projects, such as [MDN Web Docs](https://github.com/mdn/content/blob/main/.github/workflows/markdown-lint.yml), use certain GitHub Action flows to automate and quicken their code reviews. +* **Pull/Merge requests:** Where people discuss and review changes that are in progress, whether it's to improve a contributor's line of code, grammar usage, use of images, etc. Some projects, such as [MDN Web Docs](https://github.com/mdn/content/blob/main/.github/workflows/markdown-lint.yml), use certain GitHub Action flows to automate and quicken their code reviews. * **Discussion forums or mailing lists:** Some projects may use these channels for conversational topics (for example, _"How do I..."_ or _"What do you think about..."_ instead of bug reports or feature requests). Others use the issue tracker for all conversations. A good example of this would be [CHAOSS' weekly Newsletter](https://chaoss.community/news/) * **Synchronous chat channel:** Some projects use chat channels (such as Slack or IRC) for casual conversation, collaboration, and quick exchanges. A good example of this would be [EddieHub's Discord community](http://discord.eddiehub.org/). @@ -224,7 +224,7 @@ You can also use one of the following resources to help you discover and contrib * [First Contributions](https://firstcontributions.github.io) * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/) * [OpenSauced](https://opensauced.pizza/) - +* [Gilab Explore](https://gitlab.com/explore/projects/starred) ### A checklist before you contribute When you've found a project you'd like to contribute to, do a quick scan to make sure that the project is suitable for accepting contributions. Otherwise, your hard work may never get a response. @@ -307,7 +307,7 @@ Now do the same for the project's pull requests.
From 2c5a732d5cef4d0f05c4ae550af9d0cc1d72b290 Mon Sep 17 00:00:00 2001 From: Wodsfort Date: Sun, 13 Jul 2025 18:46:11 +0300 Subject: [PATCH 2/2] Change after creating mistake Signed-off-by: Wodsfort --- _articles/how-to-contribute.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md index 2965e78cf1b..ba3927103cc 100644 --- a/_articles/how-to-contribute.md +++ b/_articles/how-to-contribute.md @@ -224,7 +224,7 @@ You can also use one of the following resources to help you discover and contrib * [First Contributions](https://firstcontributions.github.io) * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/) * [OpenSauced](https://opensauced.pizza/) -* [Gilab Explore](https://gitlab.com/explore/projects/starred) +* [Gitlab Explore](https://gitlab.com/explore/projects/starred) ### A checklist before you contribute When you've found a project you'd like to contribute to, do a quick scan to make sure that the project is suitable for accepting contributions. Otherwise, your hard work may never get a response.