Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add instructions to compile binaries #2

Merged
merged 9 commits into from
Mar 14, 2024
Merged

Add instructions to compile binaries #2

merged 9 commits into from
Mar 14, 2024

Conversation

kavir1698
Copy link
Contributor

@kavir1698 kavir1698 commented Feb 26, 2024

Tests fail because the changes in #1 need to be merged first.

@kavir1698 kavir1698 requested a review from minottic February 26, 2024 15:16
Add instructions to compile binaries

Change loop syntax for Windows builds

Fix typo

Fix variable declaration

Update the build command for Windows

Fix the APPS list for PowerShell
@kavir1698
Copy link
Contributor Author

@minottic Can you check again please? This commits are squashed.

.github/workflows/go.yml Outdated Show resolved Hide resolved
@minottic minottic self-requested a review March 6, 2024 12:26
.github/workflows/go.yml Outdated Show resolved Hide resolved
.github/workflows/go.yml Outdated Show resolved Hide resolved
.github/workflows/go.yml Show resolved Hide resolved
@minottic minottic self-requested a review March 6, 2024 12:33
kavir1698 and others added 7 commits March 6, 2024 14:07
Since deploying and creating a new release are typically actions you would want to do after
code has been reviewed and merged, triggering on a pull request results to errors.
@kavir1698
Copy link
Contributor Author

@minottic the goreleaser is working. I have modified it to run in this branch just for tests. Before merging, we have to revert back to 47c59ed. After it is merged, we need to push a tag, and it should create a release with all the binaries.

@kavir1698
Copy link
Contributor Author

We have to tag the main branch after this PR is merged for the releases to be created. What would you choose as the version of the whole package? v1.0.0? or 0.1.0?

@minottic
Copy link
Member

I would do 0.1.0 for the moment

@kavir1698 kavir1698 merged commit 1c235c8 into main Mar 14, 2024
2 checks passed
@kavir1698 kavir1698 deleted the autocompile branch March 14, 2024 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants