Welcome to CommitPulse 🚀
We’re excited to be part of GSSoC 2026 and grateful to everyone contributing to CommitPulse.
To maintain a smooth contributor experience and keep the project high-quality and scalable, please read these guidelines carefully before contributing.
PRs that ignore these instructions may be closed without review.
📜 Contribution Guidelines
1. Read the CONTRIBUTING.md File
Before starting:
- read the CONTRIBUTING.md completely
- follow the setup instructions
- understand the project structure
- follow coding standards and PR guidelines
Most common contributor questions are already answered there.
2. Do Not Work On Unassigned Issues
Please do not start working on an issue unless you are officially assigned.
If you submit a PR for an issue that is:
- already assigned
- unassigned
- or being worked on by someone else
the PR may be marked as invalid and closed.
3. Issue Assignment Workflow
CommitPulse uses an automated issue management system to ensure fair contribution distribution during GSSoC.
Available Commands
/claim
Self-claim an issue.
Example:
/assign @username
Maintainers can assign contributors manually.
Example:
/unassign @username
Maintainers can remove assignments.
/addlabel
Contributors can help categorize issues using labels.
Example:
/addlabel frontend performance
4. One Active Issue Per Contributor
To prevent issue hoarding and keep contribution opportunities fair:
- contributors may only hold ONE active assigned issue at a time
- complete or unassign your current issue before claiming another
If you already have an assigned issue, additional assignment requests will be automatically rejected.
5. Inactive Assignments Are Automatically Removed
Assignments with no activity for several days may be automatically unassigned to keep issues available for active contributors.
If this happens:
- you may reclaim the issue later
- simply continue discussion on the issue thread
6. Zero Tolerance For Spam Contributions
We prioritize:
- quality
- maintainability
- meaningful improvements
The following may result in PR closure and contributor restriction:
- low-effort or meaningless PRs
- unnecessary whitespace/comment changes
- random console logs/debug code
- duplicate issues
- spam assignment requests
- AI-generated code submitted without understanding/testing
7. Follow Issue & PR Templates
When opening:
please use the provided templates and fill all required information carefully.
This helps maintainers review contributions much faster.
💡 Recommended Contribution Flow
-
Find issues labeled:
-
Read the issue carefully
-
Claim the issue using:
-
Wait for assignment confirmation
-
⭐ Star → 🍴 Fork → 💻 Code → ✅ Test → 🚀 Open PR
-
Request review and participate in discussions
🌍 Join The Community
For:
- contributor discussions
- mentorship
- implementation help
- PR support
- GSSoC coordination
join the CommitPulse Discord community:
Thank you for contributing to CommitPulse and helping build something awesome 💜
Welcome to CommitPulse 🚀
We’re excited to be part of GSSoC 2026 and grateful to everyone contributing to CommitPulse.
To maintain a smooth contributor experience and keep the project high-quality and scalable, please read these guidelines carefully before contributing.
PRs that ignore these instructions may be closed without review.
📜 Contribution Guidelines
1. Read the CONTRIBUTING.md File
Before starting:
Most common contributor questions are already answered there.
2. Do Not Work On Unassigned Issues
Please do not start working on an issue unless you are officially assigned.
If you submit a PR for an issue that is:
the PR may be marked as
invalidand closed.3. Issue Assignment Workflow
CommitPulse uses an automated issue management system to ensure fair contribution distribution during GSSoC.
Available Commands
/claimSelf-claim an issue.
Example:
/assign @usernameMaintainers can assign contributors manually.
Example:
/unassign @usernameMaintainers can remove assignments.
/addlabelContributors can help categorize issues using labels.
Example:
4. One Active Issue Per Contributor
To prevent issue hoarding and keep contribution opportunities fair:
If you already have an assigned issue, additional assignment requests will be automatically rejected.
5. Inactive Assignments Are Automatically Removed
Assignments with no activity for several days may be automatically unassigned to keep issues available for active contributors.
If this happens:
6. Zero Tolerance For Spam Contributions
We prioritize:
The following may result in PR closure and contributor restriction:
7. Follow Issue & PR Templates
When opening:
please use the provided templates and fill all required information carefully.
This helps maintainers review contributions much faster.
💡 Recommended Contribution Flow
Find issues labeled:
gssoc26good first issueRead the issue carefully
Claim the issue using:
Wait for assignment confirmation
⭐ Star → 🍴 Fork → 💻 Code → ✅ Test → 🚀 Open PR
Request review and participate in discussions
🌍 Join The Community
For:
join the CommitPulse Discord community:
Thank you for contributing to CommitPulse and helping build something awesome 💜