Skip to content

[NVSHAS-9891] Azure DevOps Remote Repository Config Information #165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sunilarjun
Copy link
Contributor

@sunilarjun sunilarjun commented Mar 26, 2025

Updating the Navigation page with Azure DevOps remote repository configuration information. Tied to NVSHAS-9891. Restructured the table as well to present the "Mandatory" fields first and "Optional" fields second.

| Owner User Name | Mandatory | The repository owner's GitHub username. |
| Repository Name | Mandatory | The repository name. |
| Organization Name | Mandatory | The name of your Azure DevOps organization. |
| Project Name | Mandatory | The Azure DevOps project that contains the repository. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this section shared between Azure & GitHub? It could be confusing because the Project Name field is not required for GitHub exports, but is required for Azure Devops exports.

Copy link
Contributor Author

@sunilarjun sunilarjun Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section is shared and after reviewing I split the table into two sections for each respective provider (commit reference). Let me know if it looks alright and thank you for reviewing!

…oning info into intro sentence.

Signed-off-by: Sunil Singh <[email protected]>
@sunilarjun sunilarjun requested a review from alopez-suse April 22, 2025 15:41
@sunilarjun
Copy link
Contributor Author

Hello @alopez-suse, are there any more edits needed here or can this be merged in following the changes? Any clarification much appreciated, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants