LowLevelDevs/FoundryOS
1
1
Fork 1
Code Issues 2 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

setup auto dev-ops #1

New Issue
Open
opened 2025-02-20 02:57:48 +00:00 by zxq5 · 3 comments
zxq5 commented 2025-02-20 02:57:48 +00:00
Owner
Copy Link
Copy Source
  • pushing a commit for main should start a build job
  • the build container needs to be running the correct cargo version and have the appropriate components installed
  • the job should build the project and output the final ISO as a release.
- [x] pushing a commit for main should start a build job - [ ] the build container needs to be running the correct cargo version and have the appropriate components installed - [ ] the job should build the project and output the final ISO as a release.
zxq5 pinned this 2025-02-20 02:58:06 +00:00
zxq5 added this to the FoundryOS project 2025-02-20 03:00:44 +00:00
zxq5 added the feature/addition label 2025-02-20 03:03:05 +00:00
zxq5 added reference main 2025-02-20 03:03:19 +00:00
nullndvoid commented 2025-02-22 03:19:11 +00:00
Contributor
Copy Link
Copy Source

Automatic releases should only happen when we git tag a new version IMO.

Cool idea though, let me know if I can help in any way.

Automatic releases should only happen when we git tag a new version IMO. Cool idea though, let me know if I can help in any way.
nullndvoid commented 2025-02-22 03:24:13 +00:00
Contributor
Copy Link
Copy Source

Nevermind, I just noticed we can just check for merges to main in order to build releases.

We should set dev branch to the default for the repo, so no one accidentally starts working on main like I started doing earlier.

Nevermind, I just noticed we can just check for merges to main in order to build releases. We should set `dev` branch to the default for the repo, so no one accidentally starts working on `main` like I started doing earlier.
zxq5 commented 2025-02-22 21:10:35 +00:00
Author
Owner
Copy Link
Copy Source

Nevermind, I just noticed we can just check for merges to main in order to build releases.

We should set dev branch to the default for the repo, so no one accidentally starts working on main like I started doing earlier.

pretty sure i protected main anyway, I'll see if i can change the default though

> Nevermind, I just noticed we can just check for merges to main in order to build releases. > > We should set `dev` branch to the default for the repo, so no one accidentally starts working on `main` like I started doing earlier. pretty sure i protected main anyway, I'll see if i can change the default though
Sign in to join this conversation.
main
Branches Tags
Labels
Clear labels
bug
crash
docs
feature/addition
No Label feature/addition
Milestone
No items
No Milestone
Projects
Clear projects
No project FoundryOS
Assignees
Clear assignees
zxq5
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LowLevelDevs/FoundryOS#1
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?