Documentation update for RDC

[amullick007]

No description provided.

[calebofearth]

Can you add tool versions for RDC analysis to the README?
EDIT: Looks like this was done.

[steph-morton]

Edits for style, clarity, punctuation, and typos.

[calebofearth]

@amullick007 looks like you'll need to merge from main to resolve the conflict on pr_hash/pr_timestamp.
I'll see if I can make this requirement a bit less onerous as we work towards 2.0.

[amullick007]

@amullick007 looks like you'll need to merge from main to resolve the conflict on pr_hash/pr_timestamp. I'll see if I can make this requirement a bit less onerous as we work towards 2.0.

I resolved the merge conflicts. Since I am not very familiar with Git, it took me few iterations to do this. Can you please check if the changes look good?

[calebofearth]

@amullick007 looks like you'll need to merge from main to resolve the conflict on pr_hash/pr_timestamp. I'll see if I can make this requirement a bit less onerous as we work towards 2.0.

I resolved the merge conflicts. Since I am not very familiar with Git, it took me few iterations to do this. Can you please check if the changes look good?

Merge looks a little funky, but seems like you caught all the file updates so I think it's good.
Now that the fileset is updated you'll need to rerun stamp_repo.sh though, as the file hash has changed. Committing those updates shouldn't have any conflicts now.
EDIT: I see you did rerun the stamp script. We should be good. Thanks!

The merge-base changed after approval.

The merge-base changed after approval.

[amullick007]

All checks have passed, @steph-morton , @Nitsirks Can you please approve this PR.

The merge-base changed after approval.

[calebofearth]

@amullick007 any idea what's going on with all these merge-base messages? It seems like approvals are being auto-dismissed for no reason.

[amullick007]

@amullick007 any idea what's going on with all these merge-base messages? It seems like approvals are being auto-dismissed for no reason.

no idea :( shall I create a new PR? Even though I am seeing that only 1 pending reviewer is left. Once @steph-morton approves the review, lets see it it allows to merge

The merge-base changed after approval.

[calebofearth]

@amullick007 any idea what's going on with all these merge-base messages? It seems like approvals are being auto-dismissed for no reason.

no idea :( shall I create a new PR? Even though I am seeing that only 1 pending reviewer is left. Once @steph-morton approves the review, lets see it it allows to merge

We may not need to abandon this PR just yet.
Give this set of command line operations a try. Assuming you have your forked repo checked out locally somewhere under the remote name 'origin' (which is default):

git switch main
git pull --ff-only
git reset --hard 7761460547e3cc36e59a6ecad457c3007f49fac7
git merge --no-commit --squash 40bd9eb6367a8cb3129074d4b951c1930952f84a
git commit -m "Squash replay of RDC documentation updates"
bash .github/scripts/stamp_repo.sh
git commit -m "Update stamps" -- .github/workflow_metadata/pr_hash .github/workflow_metadata/pr_timestamp
git push -f origin main:main

This should essentially start over from scratch and replay all your edits onto this same branch, then re-stamp it.
This will revert the merge from the chipsalliance main branch, which presumably is causing these merge-base issues.

[calebofearth]

Thanks for the fixups Avirup. Looks like it's good now. I'll merge once the checks finish.