Open EliSauder opened 1 month ago
Realized I forgot to mention it in the main PR message. This currently also includes some cleanup effort. I've removed a lot of the LICENSE files except from the root of the project and from each of the tools. I also removed old workflows, unused files, etc.
Update: I removed the dependency of having a separate PAT. GITHUB_TOKEN has permission configurations available. https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token
Update: I removed the dependency of having a separate PAT. GITHUB_TOKEN has permission configurations available. https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token
After doing some more testing I re-realized why I did the PAT method over continuing with the GITHUB_TOKEN. The reason is that with using GITHUB_TOKEN, it will not trigger workflows (i.e. the zig-master build workflow). Here is the section in the documentation about it. https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#triggering-a-workflow-from-a-workflow
Here is the specific paragraph that is relavent to enabling this ability:
If you do want to trigger a workflow from within a workflow run, you can use a GitHub App installation access token or a personal access token instead of GITHUB_TOKEN to trigger events that require a token.
Zon version overriding added. This can be removed if desired, however, based on my idea on what the publish should do, everything in the repo should be versioned together. As such, the publish workflow will now overwrite the version specified in all of the zon files with the tag that is provided.
Notes: This overwrite will only occur if the version is a semver or a semver prefixed by v.
Example generation with a tag: v0.12.2.-beta25.
Update:
Features added:
Microzig repository variables/secrets needed:
I additionally added some of the commits from #229 to enable the website to build so I could validate that it worked.
Ello, here is a done pipeline for the main zig tooling/library. It still needs the website stuff (will be working on that next).
How things work and names and everything can be changed. I just wanted to get this out here for people to start looking at.
Implemented functionality:
zig-master
with the changes.zig-master
(d)zig-master
CI Update TODO:
Microzig Repo TODO:
zig-master
branchPR_CREATE_PATPR_CREATE_TOKEN (name changed to be more accurate to what it is. see) secret for actions. This is to allow automated PR creation. The Fine-grained PAT tested with has: "Read access to metadata", and "Read and Write access to pull requests" as permissions for my fork of the microzig repository.Remarks
master-patch/{sha}
. Example: master-patch/1895868a2cf6783cd9be4653b0f99503d4c36f03. This was chosen because it prevents duplication of branch names allowing multiple patches to be open at any given time.ZEG Github Action <>
chore: commit for zig master build ci
master-patch/*
branch tozig-master
with the below details. See (b) for the main con.Testing commit {sha} with zig master
Created by Github action