docs: jj commands table

[saichandangorli1]

This commit creates the jj-commands-table.md file, containing a formatted table of frequently used jj commands. The table includes command syntax, descriptions, and practical examples to aid in understanding and using jj.

I came across your work with jj and I'd really like to contribute and help you out with it.

preview : jj-commands-table.pdf

[PhilipMetzger]

per our contributing guidelines this should be prefixed with docs: <title> (https://github.com/jj-vcs/jj/blob/main/docs/contributing.md#commit-guidelines), also mind adding it to the website with a mkdocs.yml entry?

[saichandangorli1]

per our contributing guidelines this should be prefixed with docs: <title> (https://github.com/jj-vcs/jj/blob/main/docs/contributing.md#commit-guidelines), also mind adding it to the website with a mkdocs.yml entry?

Thanks for the feedback! I've already updated the commit message with the docs: prefix and added the entry to mkdocs.yml

[PhilipMetzger]

to land your first contribution you now need to squash it all into one commit and rebase instead of merging trunk()

[saichandangorli1]

to land your first contribution you now need to squash it all into one commit and rebase instead of merging trunk()

Got it! I'm currently trying to squash my commits as you suggested, but I've run into a bit of an issue on my end. Would you be able to offer some guidance? Any help would be greatly appreciated!

[PhilipMetzger]

You already managed to squash the relevant commits into one, now the only thing you need to do is rebase instead of merging. With jj ¹, it should be easy, otherwise this video should help.

Footnotes

1. its jj abandon <first-merge-commit>::, jj git fetch, jj rebase -r <docs-rev> -d 'trunk() ↩

[saichandangorli1]

Thanks for the video link – I've already checked it out
I'm just a little unsure if I've got all the changes you mentioned quite right yet. I've also received another pull request suggestion. Should I go ahead and create a new pull request, or can you already see on your end if the changes you suggested earlier are reflected?

[PhilipMetzger]

Should I go ahead and create a new pull request, or can you already see on your end if the changes you suggested earlier are reflected?

I cannot see your now "local state" yet, as you haven't repushed the branch yet. Also you'll need to force push with Git since it will overwrite external commits.

I've also received another pull request suggestion.

What do you mean by that? As long as you follow the commit guidelines you can have as many open PRs as you want.

Should I go ahead and create a new pull request,

Not necessary if you fix this without messing up.