update iceberg procedures according to #22608

[jackychen718]

According to #22608:
Add subheading Procedures, put Register table, Unregister table, Rollback to snapshots, Expire snapshots under the subheading.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jackychen718 (7bc4d5d, c6fc84a)

[steveburnett]

Thanks for doing this! A few small nits that could be addressed while these topics are being reorganized.

[hantangwangd]

Thanks for your contribution. Maybe we should use a more specific commit title, something like:

Move the description of Iceberg procedures to a dedicated subheading

[steveburnett]

LGTM! (docs)

Pull updated branch, new local docs build, verified that all requested changes by myself and @ZacBlanco have been made in the current file.

[ZacBlanco]

Suggested change

	Rollback to Snapshots
	Rollback to Snapshot

Sorry to be pedantic - I think it should match the procedure name

[steveburnett]

When this is edited, also edit the next line "^^^^^^^^^^^^^^^^^^^^^" to match the length of the characters in the text of this line

[hantangwangd]

@jackychen718 Thanks for the fix. Please use rebase rather than merge, in that way we can remove the merge commit.

[jackychen718]

@hantangwangd Sorry for asking. I see rebase is used to merge an branch without unneccessary commit. Locally, I only have one master branch. After modify the file, could you please give some more guidance how to use rebase in the scenario.Thanks a lot.

[hantangwangd]

@jackychen718 In order to use rebase, you need a dedicated branch to synchronize with prestodb:master, then rebase your working branch which contains new commits onto it. Let's call these two branches newest and master for example. You can follow the following steps to realize a rebase:

1. git checkout -B newest // create a new branch newest based on your current working branch

2. git reset --hard HEAD~2 // hard reset all your own commits, assuming there are 2

3. git push -f origin newest // push newest to remote repository, use git remote -v to get your remote repository name, assuming the name is origin

4. Then select branch newest in your own fork repository on github, and click Sync fork -> update branch to synchronize with prestodb:master

5. git fetch origin -> git rebase origin/newest

In this way, you will rebase you working branch master onto the newest commit list without a merge. Hoping this can help you, any questions please let me know.

[jackychen718]

OK. I created another PR as described above with rebase command. Should this PR be closed?

[hantangwangd]

OK. I created another PR as described above with rebase command. Should this PR be closed?

Sure, you can close it.