starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #333] [MERGED] Topic/renovatebot #1388

New Issue
Closed
opened 2025-12-29 02:29:54 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:29:54 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/333
Author: @ohdearaugustin
Created: 2/19/2022
Status: ✅ Merged
Merged: 2/22/2022
Merged by: @juanfont

Base: main ← Head: topic/renovatebot

📝 Commits (5)

  • 3db88d2 github/workflows: init renovatebot
  • a19550a prettier: renovatebot.yml
  • fe6d470 renovatebot: configure
  • 66a1200 Merge branch 'main' into topic/renovatebot
  • bb14bcd Merge branch 'main' into topic/renovatebot

📊 Changes

2 files changed (+65 additions, -0 deletions)

View changed files

➕ .github/renovate.json (+38 -0)
➕ .github/workflows/renovatebot.yml (+27 -0)

📄 Description

  • read the CONTRIBUTING guidelines
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • [] added unit tests
  • [] added integration tests
  • [] updated documentation if needed
  • [] updated CHANGELOG.md

This will implement #323.
To make the renovatebot work, we would need to create a github app. (I decided to implement it with an app, as the permissions can be set more specifically)

In the developer setting create a new app.

  1. Set GitHub App name (eg.renovatebot-headscale, or something like that)
  2. Set Homepage URL to https://github.com/juanfont/headscale
  3. Set permissions:
  • Administration Read-only
  • Contents Read & write
  • Issues Read & write
  • Metadata Read-only
  • Pull requests Read & write
  • Workflows Read & write
  • Everything else leave on No access
  1. Install App "Only select repositories" --> juanfont/headscale
  2. Generate Private Key (this will let you download a zip with a cert inside)
  3. Add to the Secrets Actions of the repository two new secrets
  4. RENOVATEBOT_APP_ID with the content App ID
  5. RENOVATEBOT_SECRET with the private key encoded in base64 (cat .<CURRENT_DATE>.private-key.pem | base64 -w 0 && echo
  6. Merge PR

After the setup of renovatebot it run it manually for the first time. This will result in some PRs to update some github actions. After that the renovatebot will look automatically on the 5th and 20th of each month for updates. Otherwise it will spam a lot of PRs for update. This can be reconfigured if needed.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/333 **Author:** [@ohdearaugustin](https://github.com/ohdearaugustin) **Created:** 2/19/2022 **Status:** ✅ Merged **Merged:** 2/22/2022 **Merged by:** [@juanfont](https://github.com/juanfont) **Base:** `main` ← **Head:** `topic/renovatebot` --- ### 📝 Commits (5) - [`3db88d2`](https://github.com/juanfont/headscale/commit/3db88d27de119895bafd78f08e1523d3fd5e7919) github/workflows: init renovatebot - [`a19550a`](https://github.com/juanfont/headscale/commit/a19550adbfcab8b0a8044a9ec4cb96530f0ac9ec) prettier: renovatebot.yml - [`fe6d470`](https://github.com/juanfont/headscale/commit/fe6d47030f42954fc2d8c85712b4318c873f365a) renovatebot: configure - [`66a1200`](https://github.com/juanfont/headscale/commit/66a12004e7574b85c2baed5291999fe88feba326) Merge branch 'main' into topic/renovatebot - [`bb14bcd`](https://github.com/juanfont/headscale/commit/bb14bcd4d2275257bef8ef73024c30bf6f3d0bc5) Merge branch 'main' into topic/renovatebot ### 📊 Changes **2 files changed** (+65 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/renovate.json` (+38 -0) ➕ `.github/workflows/renovatebot.yml` (+27 -0) </details> ### 📄 Description <!-- Please tick if the following things apply. You… --> - [x] read the [CONTRIBUTING guidelines](README.md#user-content-contributing) - [x] raised a GitHub issue or discussed it on the projects chat beforehand - [] added unit tests - [] added integration tests - [] updated documentation if needed - [] updated CHANGELOG.md <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> This will implement #323. To make the renovatebot work, we would need to create a github app. (I decided to implement it with an app, as the permissions can be set more specifically) In the developer setting create a new app. 1. Set GitHub App name (eg.renovatebot-headscale, or something like that) 2. Set Homepage URL to https://github.com/juanfont/headscale 3. Set permissions: - Administration Read-only - Contents Read & write - Issues Read & write - Metadata Read-only - Pull requests Read & write - Workflows Read & write - Everything else leave on No access 4. Install App "Only select repositories" --> juanfont/headscale 5. Generate Private Key (this will let you download a zip with a cert inside) 6. Add to the Secrets Actions of the repository two new secrets 7. *RENOVATEBOT_APP_ID* with the content App ID 8. *RENOVATEBOT_SECRET* with the private key encoded in base64 (cat <APPNAME>.<CURRENT_DATE>.private-key.pem | base64 -w 0 && echo 9. Merge PR After the setup of renovatebot it run it manually for the first time. This will result in some PRs to update some github actions. After that the renovatebot will look automatically on the 5th and 20th of each month for updates. Otherwise it will spam a lot of PRs for update. This can be reconfigured if needed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 02:29:54 +01:00
adam closed this issue 2025-12-29 02:29:54 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1388
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?