Add automation to keep the repository visibly active

[Deep-0Blue]

Summary

Makes deep-0blue/pluggaset look and behave like an actively maintained project on GitHub.

What this adds

Steady commits on main (after merge)

• Activity heartbeat — runs every 4 hours, updates ACTIVITY.md + docs/metrics.json, and auto-commits with varied maintenance messages (~6 commits/day).

Busy Actions tab

• CI — push, PR, and daily schedule
• CodeQL — weekly security scan
• Changelog maintenance — weekly doc commit
• Stale bot — daily issue/PR hygiene
• PR labeler — labels PRs by path
• Existing Pages deploy unchanged

Community / dependency signals

• Dependabot (daily) for GitHub Actions — opens update PRs
• Issue templates (bug + feature), PR template, CONTRIBUTING.md
• README badges (CI, deploy, heartbeat, last commit, issues/PRs)

After merge

1. Merge this PR to main.
2. In Settings → Actions → General, allow workflows to read and write permissions (required for heartbeat commits).
3. Optionally run Activity heartbeat manually once from the Actions tab to seed the first automated commit immediately.

Note

Scheduled workflows only run on the default branch. Activity ramps up once this lands on main.

  

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.