A GitHub Action that updates a pinned gist with your latest GitHub activity.
activity-box is a GitHub Action that updates a pinned GitHub Gist with a user's latest activity, such as commits, issues, and pull requests. It automates the process of keeping a public gist current with recent GitHub contributions, providing a dynamic way to showcase activity on a user's profile.
GitHub users who want to automatically display their recent activity in a pinned gist on their profile, particularly developers looking to enhance their profile visibility with minimal manual effort.
Developers choose activity-box because it simplifies the process of maintaining an up-to-date activity display using GitHub's native Actions and Gists, requiring only initial setup and then running automatically on a schedule.
⚡️📌 Update a pinned gist to contain the latest activity of a user
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages GitHub Actions' schedule event to run automatically on a cron job, ensuring the gist stays updated without manual intervention, as shown in the workflow example with cron configuration.
Provides a ready-to-use template repository via the 'Use this template' button, streamlining initial configuration and reducing setup complexity for users.
Follows a minimalist philosophy, concentrating solely on updating activity data like commits and issues without bloat, making it lightweight and easy to maintain.
Uses native GitHub tools like Actions and Gists, ensuring compatibility and reducing dependencies on external services, as it's designed specifically for the GitHub ecosystem.
Requires creating and securely storing a personal access token with Gist scope, adding complexity and potential security risks if tokens are mishandled, as highlighted in the setup steps.
The activity is displayed in a plain Gist format with no built-in options for styling or advanced formatting, restricting aesthetic control and personalization.
Updates are tied to a cron schedule, meaning activity data isn't reflected in real-time and may have delays, such as the example running every 10 minutes.