Binary builds are currently available

Do NOT use them until you read this ENTIRE post

We have a CI system that does builds and uploads them we currently do not have a "release" step. You can still access the built binaries for every CI Action that was run. Each Action triggers two job for every Pull Request and every time we land a Pull Request. In order to be able to download the artifacts YOU MUST BE LOGGED IN TO GITHUB.

Look at our Actions tab in the repo to view all ci builds

Each job is named after action that caused it. This is either a Pull Request's title or a Merge of a Pull Request #### .."
Looking on the right side you can see the branch that triggered the job in blue. Look for the name of the branch you want master is the "current" code. While you can try any proposed Pull Request build, I do not recommend this unless your testing that specific Pull Request.

Each of our action events triggers two different jobs with different artifacts produced. The jobs name is visible Just below the Actions Name

• Build Tests is our general builder it makes the builds for windows, mac os and linux
• Distribution package test builds build RPM files only (maybe will in the future make others ? )

Example Action Pair

Once you pick the build you want to view you will be a on page that looks like this one Towards the bottom of the page you will see the Artifacts Section, These are the things the build produced again for some reason YOU MUST BE LOGGED INTO GITHUB or you will not be able to download them (its a github thing not us).

Using the files

Each artifact is an archive that contains one or more builds. Extract the archive and you will have an installer or another archive with the built files. (Depends on the os). All Builds currently are built in debug mode and The ubuntu 22-04 build need libei 1.2.1+. While we do not try to land bad code and have some unit tests to help prevent this. It can still happen so running the most recent master you may find some bugs that are not in the current released stable version (when this happens). Builds from Pull Request Branches Should be considered More likely to be Unstable than builds from the master branch.

I've found a bug what todo

Before you report any bugs, Always try to trigger the bug using the most recent build from the master branch. This helps us greatly many times users are running a few commits behind and we have already fixed the issue. If the Issue is still happening then you have a bug, Start by checking the issue tracker to see if its been reported We might already know about or even have Pull Request to fix the bug. If we have a PR that should fix your bug try that and report and Let us know on the Pull Request if it worked for you or not.

Bug reports on master branches builds

These issues should be reported directly to Issues. Be sure to say where you got the build and do note your set up and that you have tested this in the current code in master.

Bugs reports for Pull Request Builds.

If your using a Pull Request and you find a bug. You first have to find if the issue is in the master code or exclusive to the Pull Request, After checking for the bug in master You should also make sure you have tested in the most recent build for the Pull Request. Only than can you consider where to report the issue. If the issues is in the master build report it to Issues. If you find the issue only happens with that Pull Request's build. You should report this on the Pull Request NOT in Issues.

Where do I download the windows and the linux builds? I looked at the actions tab and I do not know what I am looking at? Are theyre direct download links? I have been using synergy/barrier for years and I am a good tester.

Maybe, add at least SOME note on the current way of getting builds into readme?

From a newcomer's perspective, the repo looks as abandoned as barrier's, but it also seems to have no builds at all. There are releases from 2021, but they have only source code, so a regular windows user looks at this and thinks: "yeah, Linux-only app". A more dedicated windows user would go to wiki, see build instructions page and think: "Ohhh... THAT kind of open-source app" (we don't expect a regular user would read wiki thoroughly, without any chapter called "install", just to see a single line that suggests checking out actions tab not even linking to it, do we?).
Only the most dedicated ones would even get to this discussion and see @sithlord48's post to realize that there actually are builds available, but they're hidden behind actions tab (completely unfamiliar to an overwhelming majority of users who aren't CI-familiar devs themselves and most likely feel really uncomfortable when they see jargon like "artifacts" and "debug").

So... maybe, at least link the post in readme?