This is Map Action github repositories
active 2024-02-13 → 2025-05-22 (UTC)
Complete coverage26,324 / 26,324 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-15 (UTC)
Events
48
Pushes
14
Pull requests
4
Issues
24
Stars
0
Forks
1
Activity over time
Daily event counts in the loaded window
Line chart, 465 days from 2024-02-13 to 2025-05-22. Pushes: 14 total, peak 5 in a day. Pull requests: 4 total, peak 3 in a day. Issues: 24 total, peak 11 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
Recent activity
Latest issues, pull requests and releases
- Issue#14Yugo192024-05-23 17:16Add either developer or user documentation to the Open Source documentation site. (Hint: Developer docs often include API docs, architecture or system state diagrams, or deployment guides.)
- Issue#13Yugo192024-05-23 17:16Use a public project management board to track progress on public tickets/issues (e.g. Taiga, GitHub/GitLab Projects, JIRA, Trello, or similar).
- Issue#12Yugo192024-05-23 17:16Create public tickets/issues that correspond to planned features and known bugs/problems with Open Source repositories.
- Issue#11Yugo192024-05-23 17:16Create contributing guidelines for all Open Source repositories. Explain how someone makes a contribution to the projects. Add to documentation website created in previous quarter.
- Issue#10Yugo192024-05-23 17:15MUST have a OSI-approved license distributed with public source code repositories by end of Q2.
- Issue#9Yugo192024-05-23 17:11Follow the Pull Request Workflow when contributing code into your Open Source repositories.
- Issue#7Yugo192024-05-23 17:11Establish an Open Source quality assurance process. Explore unit testing frameworks for front-end/back-end software, if applicable. Document user stories and test cases for games, if applicable. Document data structures and algorithm decisions for data science, if applicable.
- Issue#8Yugo192024-05-23 17:10Identify a Code of Conduct for any public Open Source repositories. Upload it to public source code repositories. Create internal documentation for how to respond to a Code of Conduct report, if one were to be made.
- Issue#6Yugo192024-05-23 17:10Create a public Open Source documentation with a corresponding public source code repository. Use automation tools to set up automatic deployments of HTML documentation site from public source code repository (e.g. with Continuous Integration).
- Issue#5Yugo192024-05-23 17:10Create READMEs (in English) for all public repositories. READMEs should include: overview of specific repo, developer environment instructions (i.e. how to set software up), note about how repo connects into overall product, list of any Open Source software used to create product (including tools and frameworks).
- Issue#4Yugo192024-05-23 17:09Create a project charter. Project charters should include: vision statement, mission statement, community statement, licensing strategy, and identification of key trademarks.
- Issue#18Yugo192024-05-21 10:26Advance Open Source quality assurance. Set up a Continuous Integration / Continuous Deployment (CI/CD) pipeline from source code repository. Set up checks or tests on new Pull Requests. Target 40% code coverage, if applicable.
- Issue#17Yugo192024-05-21 10:25Update Source Code and Documentation
- Issue#16Yugo192024-05-21 10:25Review Legal and Licensing Requirements
- Issue#15Yugo192024-05-21 10:23Advance Open Source quality assurance. Target 15% code coverage for unit tests, if applicable.
- Issue#14Yugo192024-05-21 10:23Add either developer or user documentation to the Open Source documentation site. (Hint: Developer docs often include API docs, architecture or system state diagrams, or deployment guides.)
- Issue#13Yugo192024-05-21 10:23Use a public project management board to track progress on public tickets/issues (e.g. Taiga, GitHub/GitLab Projects, JIRA, Trello, or similar).
- Issue#12Yugo192024-05-21 10:23Create public tickets/issues that correspond to planned features and known bugs/problems with Open Source repositories.
- Issue#11Yugo192024-05-21 10:23Create contributing guidelines for all Open Source repositories. Explain how someone makes a contribution to the projects. Add to documentation website created in previous quarter.
- Issue#9Yugo192024-05-20 12:12Follow the Pull Request Workflow when contributing code into your Open Source repositories.
- Issue#8Yugo192024-05-20 12:12Identify a Code of Conduct for any public Open Source repositories. Upload it to public source code repositories. Create internal documentation for how to respond to a Code of Conduct report, if one were to be made.
- Issue#7Yugo192024-05-20 12:12Establish an Open Source quality assurance process. Explore unit testing frameworks for front-end/back-end software, if applicable. Document user stories and test cases for games, if applicable. Document data structures and algorithm decisions for data science, if applicable.
- Issue#6Yugo192024-05-20 12:12Create a public Open Source documentation with a corresponding public source code repository. Use automation tools to set up automatic deployments of HTML documentation site from public source code repository (e.g. with Continuous Integration).
- Issue#5Yugo192024-05-20 12:12Create READMEs (in English) for all public repositories. READMEs should include: overview of specific repo, developer environment instructions (i.e. how to set software up), note about how repo connects into overall product, list of any Open Source software used to create product (including tools and frameworks).
- Pull request#3Yugo192024-03-05 15:31
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.