Skip to content

Conversation

@Katze719
Copy link

Changes

Adds a new GitHub Actions workflow that automatically builds and verifies the application on Linux and Windows for every pull request.

@Kenya-DK
Copy link
Owner

verifies ?

@bigrand
Copy link

bigrand commented Jan 25, 2026

verifies ?

It automatically builds the project on Windows and Linux to verify that it compiles and produces the binaries on both platforms

@Kenya-DK
Copy link
Owner

It shod not build anything on a when a pr
and it need to be sig for the auto update to work

@Katze719
Copy link
Author

It shod not build anything on a when a pr and it need to be sig for the auto update to work

Just to clarify: this workflow is intentionally only a PR build check, so we can verify that the app still compiles on Windows and Linux whenever a pull request is opened.

It does not upload any artifacts and does not perform any signing - thats not the purpose of this workflow.

@Katze719
Copy link
Author

oops, thats my mistake, wrong syntax for powershell, will fix it

@Kenya-DK
Copy link
Owner

image

@Katze719
Copy link
Author

i removed the artifact test check, but why is the windows job failing now, i dont see any logs? can you trigger or rerun the windows-job, need maintainer rights for that, i think

@Kenya-DK
Copy link
Owner

can y do in your own fork?

@Katze719
Copy link
Author

with the last commit its green on my side

@Kenya-DK
Copy link
Owner

not here :P

- Adds CI workflow that runs on pull requests
- Builds the app on Linux, Windows, and macOS
- Uses debug builds for faster CI execution
- Verifies that the app is buildable before merging
@Katze719 Katze719 force-pushed the add-github-actions-ci branch from 217bf95 to a00c646 Compare January 26, 2026 20:19
@Kenya-DK
Copy link
Owner

I stil dont see the point too it.
Since i have to build it anyway when i relesing a new build.

But for now it it fine

@Kenya-DK Kenya-DK merged commit deba7d6 into Kenya-DK:better-backend Jan 26, 2026
2 checks passed
@Mqxx
Copy link

Mqxx commented Jan 27, 2026

I stil dont see the point too it.

The workflow is just for checking if the PR would merge bad code. If you only build it after merging, it's too late, because the bad code is already on main. The workflow is designed to prevent that.

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.

4 participants