Also now the build doc has tried there's some failures you want to fix

✗  Commit checks failed:

338cc00b5 Update AUTHORS: missing newline at end of headline
e45e7deab Update DisasterRecoveryUsingBareos.rst with info on how to ingest the Catalog Backup: missing newline at end of headline
e45e7deab Update DisasterRecoveryUsingBareos.rst with info on how to ingest the Catalog Backup: headline too long

Thanks for the hints!
As I have no idea how to edit existing commit messages, I will re-open a new PR with the new changes and proper line endings.

Reopened, fixes will goes there as all the other parameters are already in place. (tagging project labels etc)

To change your commit you may simply want to rebase and adjust the changes.
We normally don't like to have a force push but in that case as there's only 2 commits, it will not be important.

So in your clone, be sure you have a fresh master (git switch master && git pull) then back to your branch you can
play with git rebase -i master

Use the reword and edit to apply your changes then you should be able to git push --force your branch

We are working on a way to allow external contributor to have access to build result, I will take care of the message after your submission.

We have this section into the documentation that may help
https://docs.bareos.org/master/DeveloperGuide/gitworkflow.html#commit-message-guideline

For example your commit to the rst can have as subject

doc: improve section recovering Bareos server section

With a body like

Add examples how to load the restored database ascii dump as catalog.

So the subject is short enough (around 50 char) but explicit for the changelog.
(you may want to consult the existing to find similar commit)

Once you have it done, you should also modify the title pr here so it can be also used during the merge.
Don't hesitate to ask help if needed.

I think I managed to change it properly. Thanks for all the tips, I already learned a lot more about git!

Build still failing :/

Build still failing :/

No in fact, the final review is now needed (which I will take care of today).

Build still failing :/

No in fact, the final review is now needed (which I will take care of today).

And I will fix the warning of our pr-tool
Commit checks failed:
b240112 docs: improve section recovering Bareos server section: body contains line longer 72 chars

If you want to contribute more, it will be interesting to setup a dev environment (see documentation it should be complete), you will find our tools in the devtools subdir.

Thanks for the help!