Hi I tried the flight-deck and I'm struggling to make use of it. Here is what I did:
1) Login to https://flight-deck.debian.net/ and select import of golang-github-adamkorcz-go-fuzz-headers-1 which is a small unimportant project that can be used for testing. 2) It created a merge request for me: https://salsa.debian.org/go-team/flight-deck/-/merge_requests/46 3) I'm unable to understand what to do next, so I tried in sequence: 3a) Click the 'Approve' button on the merge request. The text says 'Apply the changes (manual approval required)' but I'm not sure who is responsible for that manual approval or how to do it. That didn't do anything. 3b or 3c) (can't remember the order here) Go to the pipeline and manually run the 'apply-mr' job which was marked as manual. It ran but I did not see anything happen. 3b or 3c) Click to merge the request. That merged the patch, and a new pipeline was launched that failed: https://salsa.debian.org/go-team/flight-deck/-/pipelines/1001032 4) What next? I see no action on https://salsa.debian.org/go-team/packages/golang-github-adamkorcz-go-fuzz-headers-1 and I'm not sure what the even expect. Will it propose a merge request for that project? Will it apply changes automatically? Is there a panel to login into somewhere to manage the project? I think I'm missing some basic understanding of what this is and what it can do, and this suggest that the intro text on https://salsa.debian.org/go-team/flight-deck and the workflow of https://flight-deck.debian.net/ could be improved to explain things more. /Simon Otto Kekäläinen <[email protected]> writes: > Hi all! > > Changed the title to make the recommendation here more visible: please > try using flight-deck.debian.net next time you want to create a new > package or ensure the config on an existing repository is consistent. > > Arthur has been polishing flight-deck.debian.net for several months > now, and I strongly recommend everyone to try it out. It is superior > to old ways of managing team repositories in bulk and replaces error > prone scripts like > https://salsa.debian.org/go-team/infra/pkg-go-tools/-/blob/master/scripts/salsa-enable-instance-runners.sh, > and also it replaces the no-authentication create-salsa-project > endpoint with something that ensures people creating repositories at > least have a Salsa account. > > All changes can also be reviewed to decrease chances of errors in a > preventive way, and in case of any issues the fact that all changes > are in git and all executions are logged in CI makes the system as a > whole more managed, transparent and secure. > > There are still some rough edges to polish but those will be finalized > only if more people try using it and we have more people voicing their > opinions in the issues at > https://salsa.debian.org/go-team/flight-deck/-/issues > > > On Sat, 3 Jan 2026 at 15:26, Arthur Diniz <[email protected]> wrote: >> >> If you guys want to try something new, there is flight-deck. >> >> https://flight-deck.debian.net >> >> Source: https://salsa.debian.org/go-team/flight-deck >> >> It's does the same thing as create-salsa-project but it also keeps the repo >> configuration as .hcl files and compliant with the go-team standards. >> >> On Sat, Jan 3, 2026, 11:18 PM Simon Josefsson <[email protected]> wrote: >>> >>> Vincent Blut <[email protected]> writes: >>> >>> > P.S. It seems dh-make-golang create-salsa-project $project do not work >>> > at the moment. Does anyone know the cause of the problem? >>> >>> Indeed, I see this too. Maybe some stale access token, permission >>> issue, or some broken proxy service? I never understood how that >>> command work, and it smells a bit (where does it get access to salsa >>> from?). >>> >>> /Simon >
signature.asc
Description: PGP signature
