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

[PR #1809] [MERGED] update gh workflow actions #2330

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

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/1809
Author: @vdovhanych
Created: 3/3/2024
Status: ✅ Merged
Merged: 3/13/2024
Merged by: @kradalby

Base: main ← Head: actions-update-and-cleanup

📝 Commits (1)

  • 473cff5 update gh workflow actions

📊 Changes

11 files changed (+99 additions, -93 deletions)

View changed files

📝 .github/workflows/build.yml (+14 -16)
📝 .github/workflows/check-tests.yaml (+11 -11)
📝 .github/workflows/contributors.yml (+2 -1)
📝 .github/workflows/docs.yml (+4 -2)
📝 .github/workflows/gh-actions-updater.yaml (+2 -3)
📝 .github/workflows/lint.yml (+31 -31)
📝 .github/workflows/release.yml (+3 -3)
📝 .github/workflows/stale.yml (+2 -1)
📝 .github/workflows/test-integration.yaml (+17 -13)
📝 .github/workflows/test.yml (+12 -11)
📝 .github/workflows/update-flake.yml (+1 -1)

📄 Description

What is changed by this PR:

  • Updates the various actions used for the projects workflows
  • Changes the tj-actions/changed-files to better maintained action dorny/paths-filter usage is basically the same and from what i tested its working as expected.
    • This also allows a better granularity for the file filters with more options to conditionally run what is needed.
      - name: Get changed files
    id: changed-files
    uses: dorny/paths-filter@v3
    with:
      filters: |
        yaml-files:
          - 'config-example.yaml'
        go-files
          - '**/*.go'
        nix-files
          - '*.nix'
    and the you can use it with steps.changed-files.outputs.<filter-name> == 'true' to run it only if the files from that filter were changed.
  • Small adjustments to file formatting

As next step i would like to introduce some naming conventions for the action files, workflow names and so on. But this is more upt to you guys if youd like that change.

  • 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 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/1809 **Author:** [@vdovhanych](https://github.com/vdovhanych) **Created:** 3/3/2024 **Status:** ✅ Merged **Merged:** 3/13/2024 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `actions-update-and-cleanup` --- ### 📝 Commits (1) - [`473cff5`](https://github.com/juanfont/headscale/commit/473cff5fa630a2f8804798de6964ed6ae3af8a03) update gh workflow actions ### 📊 Changes **11 files changed** (+99 additions, -93 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build.yml` (+14 -16) 📝 `.github/workflows/check-tests.yaml` (+11 -11) 📝 `.github/workflows/contributors.yml` (+2 -1) 📝 `.github/workflows/docs.yml` (+4 -2) 📝 `.github/workflows/gh-actions-updater.yaml` (+2 -3) 📝 `.github/workflows/lint.yml` (+31 -31) 📝 `.github/workflows/release.yml` (+3 -3) 📝 `.github/workflows/stale.yml` (+2 -1) 📝 `.github/workflows/test-integration.yaml` (+17 -13) 📝 `.github/workflows/test.yml` (+12 -11) 📝 `.github/workflows/update-flake.yml` (+1 -1) </details> ### 📄 Description <!-- Headscale is "Open Source, acknowledged contribution", this means that any contribution will have to be discussed with the Maintainers before being submitted. This model has been chosen to reduce the risk of burnout by limiting the maintenance overhead of reviewing and validating third-party code. Headscale is open to code contributions for bug fixes without discussion. If you find mistakes in the documentation, please submit a fix to the documentation. --> What is changed by this PR: - Updates the various actions used for the projects workflows - Changes the `tj-actions/changed-files` to better maintained action `dorny/paths-filter` usage is basically the same and from what i tested its working as expected. - This also allows a better granularity for the file filters with more options to conditionally run what is needed. ```yaml - name: Get changed files id: changed-files uses: dorny/paths-filter@v3 with: filters: | yaml-files: - 'config-example.yaml' go-files - '**/*.go' nix-files - '*.nix' ``` and the you can use it with `steps.changed-files.outputs.<filter-name> == 'true'` to run it only if the files from that filter were changed. - Small adjustments to file formatting As next step i would like to introduce some naming conventions for the action files, workflow names and so on. But this is more upt to you guys if youd like that change. <!-- Please tick if the following things apply. You… --> - [x] read the [CONTRIBUTING guidelines](README.md#contributing) - [ ] 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. --> --- <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 03:20:48 +01:00
adam closed this issue 2025-12-29 03:20:48 +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#2330
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?