I’m trying to commit a codeabbey challenge on Gitlab but the test pipeline keeps failing.
What do you understand or find about that problem
Yesterday I made a commit to my branch in the challenges repo, however due to a typo in the commit message and a duplicate solution for a language in the OTHERS.lst file the pipeline failed; today I fixed these issues and tried to do it again after checking the local build, however the repo now expects a challenge with a higher score and also due to the attempts and checks some of the pastebin links in the OTHERS.lst file started returning Http status 429 instead of 200.
You make any workaround? What did you do?
Last night I reverted the commit at fault since the test pipelines were not letting me fix an issue with the OTHERS.lst file separately.
(Optional) Why fails your workaround?
The repo still expects me to submit a higher score challenge despite me not being able to even merge the current challenge, not to mention the pastebin links will randomly return status 429 and cause the test pipeline to fail, I tried changing some of the links and sorted them but due to a VSCode screwup it sent an invalid link again with the current commit.
Link to current commit
Link to pipeline result
I need help with
Reverting the commit in a proper way and resetting the test policy so I can send and merge this challenge once and for all, and a preferred alternative to store raw code and avoid getting hit by status 429 would be nice