r.out.ascii: Create an option to write a LISFLOOD compatible header

[YannChemin]

The option applied by the "-l" flag permits to write an ASCII grid file compatible with the European LISFLOOD model (https://ec-jrc.github.io/lisflood-model/1_1_introduction_LISFLOOD/)

[echoix]

For your next PRs, you'll have more luck by not using the main branch of your fork for a PR

[YannChemin]

For your next PRs, you'll have more luck by not using the main branch of your fork for a PR

Do you mean something like that?

git checkout -b something-branch
git add something
git commit -m "that something is changed"
git push -u origin something-branch
gh pr create --base main --head something-branch --fill

[echoix]

For your next PRs, you'll have more luck by not using the main branch of your fork for a PR

Do you mean something like that?

git checkout -b something-branch
git add something
git commit -m "that something is changed"
git push -u origin something-branch
gh pr create --base main --head something-branch --fill

Yep, seems right

[echoix]

I'm not sure changing the relative markdown links from ending with ".md" to ending with ".html" is expected.

[echoix]

Other questions on markdown syntax

[nilason]

@echoix Any objections to merge?

[echoix]

@echoix Any objections to merge?

Apart from the fact that the PR comes from his main branch, probably not

[nilason]

@echoix Any objections to merge?

Apart from the fact that the PR comes from his main branch, probably not

Although not good practice, it wouldn’t mess things up, would it?

[echoix]

@echoix Any objections to merge?

Apart from the fact that the PR comes from his main branch, probably not

Although not good practice, it wouldn’t mess things up, would it?

Not that much what we can't survive. He'll need to use the GitHub UI to "discard x commits" on his fork to update his main after, then clean up locally too, or reclone if he doesn't want to bother finding how to discard his commits on main

Will keep this branch