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

Upload build artefact after master/pr builds #45

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

Originally created by @kradalby on GitHub (Oct 6, 2021).

Github actions supports having build artefacts published after each build and "stored" on the job like this (scroll down to Artefacts)

This is done afaik with actions/upload-artifact.

It would be very neat to have this published on all main branch builds and PR builds.
This would make it significantly easier for people to test builds from PRs and master without having to pull down the code and build it.
It would also make it easier for users in general to track main and help us catch bugs before doing releases.

Originally created by @kradalby on GitHub (Oct 6, 2021). Github actions supports having build artefacts published after each build and "stored" on the job like [this](https://github.com/neovide/neovide/actions/runs/1306426310) (scroll down to Artefacts) This is done afaik with [actions/upload-artifact](https://github.com/actions/upload-artifact). It would be very neat to have this published on all `main` branch builds and PR builds. This would make it significantly easier for people to test builds from PRs and master without having to pull down the code and build it. It would also make it easier for users in general to track `main` and help us catch bugs before doing releases.
adam added the enhancementhelp wanted labels 2025-12-29 01:21:00 +01:00
adam closed this issue 2025-12-29 01:21:00 +01:00
adam commented 2025-12-29 01:21:01 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Oct 6, 2021):

@ohdearaugustin would you be up for having a look at this if you agree that the feature is useful?

@kradalby commented on GitHub (Oct 6, 2021): @ohdearaugustin would you be up for having a look at this if you agree that the feature is useful?
adam commented 2025-12-29 01:21:02 +01:00
Author
Owner
Copy Link

@ohdearaugustin commented on GitHub (Oct 6, 2021):

I can take a look at it, probably on the weekend. (=

@ohdearaugustin commented on GitHub (Oct 6, 2021): I can take a look at it, probably on the weekend. (=
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 enhancement help wanted
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#45
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?