- What is graham-campbell/github-notifications used for?
- It is a Laravel service-provider package that exposes Artisan commands for triaging GitHub notifications, such as listing, filtering by reason, and marking threads as read or done. It is developer tooling rather than an embeddable library: there is no public API, event system, or meaningful extension point. Use it for internal productivity or ops automation, not on a customer-facing request path.
- How do I install graham-campbell/github-notifications in Laravel?
- Install it with Composer, let Laravel package discovery register the service provider, publish any config file, and set a GitHub token in .env or your secret store. Confirm the package's Laravel and PHP constraints against your baseline before assuming it installs cleanly. For safety, add it as a require-dev dependency or isolate it in a small internal devtools repository or scheduled workflow.
- Which GitHub token scopes and account should I use with graham-campbell/github-notifications?
- The GitHub notifications API is per-authenticated-user, and the token needs notification read and write scope. Prefer a dedicated machine account with a fine-grained personal access token scoped only to notifications, stored in a secret manager and rotated on a defined cadence. Avoid using a personal token that belongs to whichever engineer set it up.
- Does graham-campbell/github-notifications support multiple users or organization-wide notifications?
- No. GitHub's notifications API has no organization-wide view; it returns notifications for the authenticated user only. Supporting several engineers means managing one token per engineer or sharing a bot account, and a bot's notifications are not a human's notifications, which creates privacy and audit concerns.
- What Laravel and PHP versions does graham-campbell/github-notifications support?
- Graham Campbell's packages generally track current Laravel majors, but this package has zero dependents and no downstream pressure when versions drift. Check the composer.json constraints and Packagist release history before assuming compatibility. Verify the install in a dev container or CI job against your exact Laravel and PHP baseline.
- Is graham-campbell/github-notifications safe to use in production?
- It is not a good fit for production runtime or any customer-facing path because it provides tooling, not an application API. The risk profile is high for the value delivered: bus factor one, zero ecosystem validation, and a thin wrapper over a historically unstable GitHub notifications surface. Isolate it as require-dev or internal automation, and add alerting because failures are silent: notifications simply accumulate.
- Does graham-campbell/github-notifications persist state or publish migrations?
- The evaluation asks you to confirm whether the package persists state such as a database table or cache keys, and whether it publishes migrations or config keys that collide with yours. If it does persist state, you own the migration and a cleanup job. Review the service provider and config before installing it into an existing application.
- How do I test graham-campbell/github-notifications?
- Mock GitHub API responses with HTTP fakes or recorded fixtures and run the Artisan commands in CI; use a dedicated test token only against a sandbox account if needed. Check whether the repository has a test suite and review its last release date, commit cadence, and open-issue posture. With no dependents, you are responsible for proving it works on your stack.
- What are alternatives to graham-campbell/github-notifications?
- Alternatives include the GitHub CLI's notification commands, the GitHub web UI, custom scripts against the notifications API, or reducing notification noise at the source by fixing noisy bots and CI. Because the package logic is thin, reimplementing the few commands you need may be cheaper than forking. Lock-in is low either way.
- How do I handle maintenance if graham-campbell/github-notifications goes dormant?
- Plan for dormancy up front by pinning the version, monitoring GitHub API changes, and deciding whether to fork or reimplement if the maintainer stops updating it. A fork is possible, but the wrapper is thin enough that reimplementation is likely cheaper. Also add a failure alert, since a broken notification tool fails silently by letting unread notifications pile up.