Add initial PackIt config #271
Conversation
|
@marcan note that this won't do anything until PackIt is setup for the AsahiLinux org. To do that, follow https://packit.dev/docs/guide/ If this goes well I plan to add it for the other projects we have packaged in Fedora. |
marcan
force-pushed
the
main
branch
3 times, most recently
from
06224ed to
88b1866
Compare
marcan
force-pushed
the
main
branch
2 times, most recently
from
f0edbd9 to
50c808d
Compare
|
@davide125 Hello Davide! Just randomly got to this PR -- if there's anything missing from Packit's side or you need any help, let us/me know! |
|
I think I can just merge this right? Anything else to do on the side of this repo? |
|
We can merge it but it won't do anything useful until the AsahiLinux github org is onboarded on PackIt. To do that follow the instructions on https://packit.dev/docs/guide/#1-set-up-packit-integration (it basically amounts to installing a github app and then waiting for the ticket to be approved on the packit side). |
marcan
force-pushed
the
main
branch
3 times, most recently
from
4f95305 to
95d67cf
Compare
davide125
force-pushed
the
packit
branch
2 times, most recently
from
c1e357d to
6d5258e
Compare
Signed-off-by: Davide Cavalca <[email protected]>
|
Can we limit the build targets to |
As suggested by @jannau in AsahiLinux#271 (comment) Signed-off-by: Davide Cavalca <[email protected]>
Sure, put up #443 for that. |
As suggested by @jannau in #271 (comment) Signed-off-by: Davide Cavalca <[email protected]>
This adds an initial config so we'll get per-commit and per-PR package builds published at https://copr.fedorainfracloud.org/coprs/g/asahi/packit-builds/ which should make testing easier and provide useful signal in case of regressions.