ProjectHive automatically tracks contributors and updates the leaderboard and Hall of Fame when pull requests are merged.
When you create a project, you must include this line in your project's README.md:
**Contributor:** YourGitHubUsernameThe automation script recognizes several formats:
✅ **Contributor:** username
✅ **Contributor**: username
✅ Contributor: **username**
✅ Contributor: username
# My Awesome Project
**Contributor:** john-doe
## Description
This is my awesome project that does amazing things!
## Tech Stack
- React
- Node.js
- MongoDB
## How to Run
1. Clone the repository
2. Run `npm install`
3. Run `npm start`❌ Don't use placeholder names:
**Contributor:** YourUsername**Contributor:** YourGitHubUsername**Contributor:** username
✅ Use your actual GitHub username:
**Contributor:** john-doe**Contributor:** jane-smith
❌ Don't forget the Contributor line: Without this line, your contribution won't be counted!
❌ Don't use special characters in incorrect places:
**Contributor::** username(double colons)Contributor username(missing colon)
- Submit PR: Create your pull request with your project.
- PR Merged: Wait for a maintainer to review and merge your PR.
- Automatic Update: Within 2-3 minutes of merge, GitHub Actions will:
- Scan all project files
- Find your contributor tag
- Update the leaderboard
- Update the Hall of Fame (if you're in top 10)
- Shows all contributors ranked by total contributions
- Displays domains you've contributed to
- Updates automatically with each merged PR
View: DomainsLeaderboards/Overall.md
- Features the top 10 contributors
- Displays your GitHub profile picture
- Shows your total contributions and domains
View: HallOfFame/README.md
Check these things:
-
Did you include the contributor tag?
- Open your project's README.md
- Look for
**Contributor:** YourUsername - Make sure your actual GitHub username is there
-
Is your username formatted correctly?
- GitHub usernames can only contain alphanumeric characters and hyphens
- They cannot start or end with a hyphen
- Maximum 39 characters
-
Wait a few minutes
- The GitHub Actions workflow takes 2-3 minutes to complete
- Check the Actions tab to see if the workflow is still running
-
Check the workflow logs
- Go to the repository's "Actions" tab
- Click on the latest "Update Leaderboard" workflow
- Check if there were any errors
If you see a failed workflow:
-
Check the error message in Actions tab
-
Common issues:
- Permission errors: The workflow may need additional permissions
- File not found: Make sure your files are in the correct directories
- Invalid format: Check that your contributor tag follows the correct format
-
Contact maintainers:
- Open an issue on the repository
- Provide your PR number and username
- A maintainer can manually trigger the workflow
If the automatic update fails, you can manually trigger the workflow:
- Go to the "Actions" tab
- Click "Update Leaderboard" workflow
- Click "Run workflow"
- Select the branch and click "Run workflow"
The workflow requires these permissions:
contents: write- To commit leaderboard updatespull-requests: read- To read PR information
These are configured in .github/workflows/leaderboard.yml.
- Contribute to multiple domains - Your contributions across different domains are all counted
- Quality over quantity - Well-documented, functional projects are valued
- Help others - Reviewing PRs and helping newcomers builds community reputation
- Be consistent - Regular contributions throughout Hacktoberfest
Happy Contributing! 🚀