Use reference with API requests to protect against mid-air collisions
reference parameter allows the API to verify that the current state in the database matches the state expected by the consumer.
There is https://gitlab.suse.de/qsf-u/qa-sle-functional-userspace/-/merge_requests/29 and no one responded within 3 weeks. This is either a big overlook on the side of the corresponding team or they just don't like you ;) In any case also the pipeline job seems to have failed. So what do you plan as next steps?
Turns out git/ GitLab CI is making what should've been a simple fix quite a challenge.
- There's no
origin/masteron GitLab CI
git fetchfails because it's not configured
git showdoesn't fail even when it fails
CI_COMMIT_BEFORE_SHAdoesn't work and isn't well-documented
I think it's not very nice having to compose the repo URL ourselves, but it works.
#11 Updated by cdywan about 1 month ago
- Status changed from In Progress to Feedback
There's also an alternative proposal https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/166 which means this is pending on upstream's call on which to go for now.
No update in the MR https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/166 but I guess we can just give it more time.