fix: namespace parsing in gitlab

[shyim]

Thank you for submitting this pull request

URLs like https://gitlab.shopware.com/shopware/6/product/commercial/-/merge_requests/1645
cannot be parsed right now as the extractor expects only one path in "namespace". But we have in our org nested stuff

Referenced pull requests

Checklist

• Tests added if applicable.
• Documentation updated if applicable.

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows git conventional commits pattern, therefore the commits should have the following format:

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

NOTE: if you are still in a work in progress branch and you want to push your changes remotely, consider adding --no-verify for both commit and push, e.g., git push origin <feat-branch> --no-verify - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please amend the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.

Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.

More details can be found in package release section of the README.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	90.05% (+0.14% 🔼)	389/432
🟢	Branches	83.06%	152/183
🟢	Functions	88.5%	100/113
🟢	Lines	90% (+0.12% 🔼)	378/420

Test suite run success

159 tests passing in 16 suites.

Report generated by 🧪jest coverage report action from a3814cb

[lampajr]

Thanks a lot for this contribution @shyim !

Going to take a look at this asap 🚀

[lampajr]

Hey @shyim , the change looks great to me.
I just added a simple test to ensure the result is the expected one, do you mind to double check it: a3814cb ?

After that, unfortunately I do not have any real nested scenario to test against, so if you have your concrete example I would appreciate if you can run the cmd line tool against your own nested repo to check if that works as expected - you can just npm run compile and then call the cmd line tool (maybe you already did that :) ).

[shyim]

Hey,

I have tested it works great. 👍

[lampajr]

lgtm! Thanks again @shyim for your contribution ❤️

[shyim]

Could you maybe tag a new version? I would like to integrate it in our pipeline ❤️

[lampajr]

Could you maybe tag a new version? I would like to integrate it in our pipeline ❤️

Here it is https://github.com/kiegroup/git-backporting/releases/tag/v4.4.1 and https://www.npmjs.com/package/@kie/git-backporting/v/4.4.1