You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, we can quickly trigger some builds by issuing PRs and commits without waiting to be merged into the main branch. The advantage of this is that build errors can be excluded during the PR stage. A feasible solution is to set up a GitHub workflow and associate it with the build server to wait for the build server to return the status, so as to feedback to the developer.
I have no experience with building on Arch, so forgive my ignorance here. I have some experience setting up Github workflows, so if there is some guidance I might know how to do it.
The text was updated successfully, but these errors were encountered:
This issue is that the build environment isn't fully contained---Due to the way devtools is implemented, privilege escalation could be done. And if that's too hard for script kids, resource exhaustion would be no problem.
However, you can use triggerabuild to manually trigger a lilac build for select people (i.e. people in a github organization). The code needs to be on master though.
In some cases, we can quickly trigger some builds by issuing PRs and commits without waiting to be merged into the main branch. The advantage of this is that build errors can be excluded during the PR stage. A feasible solution is to set up a GitHub workflow and associate it with the build server to wait for the build server to return the status, so as to feedback to the developer.
I have no experience with building on Arch, so forgive my ignorance here. I have some experience setting up Github workflows, so if there is some guidance I might know how to do it.
The text was updated successfully, but these errors were encountered: