DOC: Fixup nvtools migration message

[carterbox]

Description:

Tweaking the NVIDIA Tools migrator to fix formatting in the commit message and to add title, commit message, and branch name.

Checklist:

• Pydantic model updated or no update needed

Cross-refs, links to issues, etc:

[carterbox]

Merge if passing

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 76.83%. Comparing base (604d177) to head (9bfa9fa).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
conda_forge_tick/migrators/nvtools.py	50.00%	5 Missing ⚠️

❌ Your patch status has failed because the patch coverage (50.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3911      +/-   ##
==========================================
- Coverage   76.85%   76.83%   -0.02%     
==========================================
  Files         137      137              
  Lines       15344    15351       +7     
==========================================
+ Hits        11792    11795       +3     
- Misses       3552     3556       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[beckermr]

This will reissue all PRs the migrator ever made. Did you mean to do that?

We almost never due that because it is a bit spammy.

[jakirkham]

Think that is ok. We are the ones creating and receiving the spam

[carterbox]

This is good to know for the future. Luckily only a few PRs had been opened, so there were few duplicates. How do you update an in-progress migrator, then? i.e. have the bot rerun unedited pull requests?

[beckermr]

Well you have two choices.

1. Leave the migrator_version as is and the bot will use the updates for new PRs, but leave old ones alone.
2. Bump the migrator_version and get new PRs for everything.

There is no feature to go back and edit pull requests already issued.

[jakirkham]

As a future note let's also link the main issue so it is easier to track all the migration PRs that are made and see when they are closed out

Suggested change

	Please ping carterbox for questions.
	Please ping carterbox for questions.
	xref: https://github.com/conda-forge/cuda-feedstock/issues/62

[carterbox]

That's a good point, since the migrations tracking page doesn't update immediately.