Update how-to guide for commit workflow

[RaghvendraMandawale]

guidance and recommendation on when not to trigger discard operation.

[prmerger-automator]

@RaghvendraMandawale : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @sushantjrao

[learn-build-service-prod]

Learn Build status updates of commit 4405f22:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/operator-nexus/howto-use-commit-workflow-v2.md	✅Succeeded

For more details, please refer to the build report.

[RaghvendraMandawale]

#sign-off (public repo)

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @sushantjrao

[ttorble]

@RaghvendraMandawale

This pull request was opened in the public repo and only the listed author can sign off on updates. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

@scottsteinbrueck

Can you review the proposed changes or assign a new author? For the author to be able to sign off, they will need to update the author metadata value in a PR in the private repo.

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[RaghvendraMandawale]

Hi @ttorble , yes. I will make future content changes in the private repo. Could you please share some guidelines or an article here on how this should be done? I’m new to this space.
Also, my teammate Sushant Rao, who used to work on this part, is no longer with the organization. I’ll be managing the Learn documentation going forward. Could you let me know how I can get explicit edit (Author) access to the repositories relevant to my team?
Thanks!

[ttorble]

Hi @RaghvendraMandawale

Here's some information about working in the private repos:

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

Note that the contributor guidance has moved to https://learn.microsoft.com/help/
To access the guides, you must log in with your Learn profile. If you don't have a Learn profile, follow the instructions at Manage your Microsoft Learn profile settings | Microsoft Learn to create one.

Once you're set up, you can fork and clone any private repo and create PRs there to change the author details on the articles you'll be taking over from Sushant. You'll have full access to do that in the private repos. After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged. 

I recommend you also recreate this PR in the private repo. This PR now has merge conflicts and you can sign off as the author in the private repo without waiting for further approval. If you decide to do that, please close this PR.

I hope this helps. You can also ask for help in the Learn support channel in Teams.

Thanks!