Skip to content

Conversation

bkeryan
Copy link
Collaborator

@bkeryan bkeryan commented Mar 26, 2025

  • This contribution adheres to CONTRIBUTING.md.
  • I've updated CHANGELOG.md if applicable.
  • I've added tests applicable for this pull request

What does this Pull Request accomplish?

Add GitHub issue templates based on https://github.com/ni/ni-apis/tree/main/.github/ISSUE_TEMPLATE

Add a GitHub Actions workflow that syncs GitHub issues to Azure DevOps using https://github.com/danhellem/github-actions-issue-to-work-item
The workflow is based on https://github.com/ni/measurement-plugin-python/blob/main/.github/workflows/sync_github_issues_to_azdo.yml

I also created tech debt and user story labels (separate from this PR).

Why should this Pull Request be merged?

Provide more guidance for which information to include in bug reports.

Automatically sync bug reports to Azure DevOps so they get more visibility.

What testing has been done?

None

@bkeryan bkeryan changed the title github; Add issue templates and GitHub->AzDO issue syncing github: Add issue templates and GitHub->AzDO issue syncing Mar 26, 2025
@zhindes zhindes requested a review from hongloonwong March 26, 2025 17:56
@zhindes
Copy link
Collaborator

zhindes commented Mar 26, 2025

@bkeryan - I added @hongloonwong as a reviewer. Let's make sure he's happy with this before merging.

Copy link
Contributor

Test Results

    34 files  ±0      34 suites  ±0   54m 4s ⏱️ - 2m 50s
 2 396 tests ±0   2 042 ✅ ±0    354 💤 ±0  0 ❌ ±0 
43 102 runs  ±0  36 850 ✅ ±0  6 252 💤 ±0  0 ❌ ±0 

Results for commit 21b70d2. ± Comparison against base commit 11cefd7.

Copy link
Collaborator

@hongloonwong hongloonwong left a comment

Choose a reason for hiding this comment

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

I like this especially the GitHub Issues synced to AzDO Bug. My team discussed about this last year on how to better on top of the nidaqmx-python issues using AzDO work item.

@bkeryan bkeryan merged commit 62fc525 into master Mar 27, 2025
17 checks passed
@bkeryan bkeryan deleted the users/bkeryan/github-issue-templates-and-syncing branch March 27, 2025 13:54
wchung-ni added a commit to ni/nisync-python that referenced this pull request Apr 23, 2025
- [X] This contribution adheres to
[CONTRIBUTING.md](https://github.com/ni/nisync-python/blob/main/CONTRIBUTING.md).

### What does this Pull Request accomplish?
With reference to the content of [DAQmx
PR](ni/nidaqmx-python#686)
- Add GitHub issue template based on
https://github.com/ni/ni-apis/tree/main/.github/ISSUE_TEMPLATE
- Add a GitHub Actions workflow that syncs GitHub issues to Azure DevOps
using
[https://github.com/danhellem/github-actions-issue-to-work-item](https://github.com/danhellem/github-actions-issue-to-work-item)
The workflow is based on [
https://github.com/ni/measurement-plugin-python/blob/main/.github/workflows/sync_github_issues_to_azdo.yml](https://github.com/ni/measurement-plugin-python/blob/main/.github/workflows/sync_github_issues_to_azdo.yml)
- By referring daqmx, I created two new labels(tech debt and user story)
before this PR is merged.
- What is difference from [DAQmx
PR](ni/nidaqmx-python#686)

1.
'[ado_area_path](https://github.com/ni/nisync-python/pull/21/files#diff-202df4d842092333fc71217d929c58e696a315f3ae8415b32b5650adf1af9b28:~:text=ado_area_path%3A%20%22DevCentral%5C%5CProduct%20RnD%5C%5CPlatform%20HW%20and%20SW%5C%5CCore%20SW%20and%20Drivers%5C%5CPlatform%20HW%20and%20Drivers%5C%5CDrivers%5C%5CMars%22)'
: Area path of reported issue in Azure DevOps
2. package name in[
bug_report.md](https://github.com/ni/nisync-python/pull/21/files#diff-185833cb26d7ac66a4d39042fd576a820c2c2c6d05ad18973bb9c7dce77267c5:~:text=*%20NI%2DSync,nisync%2Dpython%60)

### Why should this Pull Request be merged?
Provide more guidance for which information to include in bug reports.
Automatically sync bug reports to Azure DevOps so they get more
visibility.

### What testing has been done?
None

Signed-off-by: wchung <[email protected]>
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.

3 participants