Skip to content
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

GitHub Issue trigger - [ ] does not work #6007

Open
jorishijmans opened this issue May 17, 2024 · 0 comments
Open

GitHub Issue trigger - [ ] does not work #6007

jorishijmans opened this issue May 17, 2024 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@jorishijmans
Copy link

  • Extension version: GitHub Actions v0.26.2
  • VSCode Version: Version: 1.89.1 (user setup)
  • OS: Windows_NT x64 10.0.22631
  • Repository Clone Configuration (single repository/fork of an upstream repository):
  • Github Product (Github.com/Github Enterprise version x.x.x): Pro

Steps to Reproduce:

  1. Open settings in VS Code with CTRL + ,
  2. Search issue in settings and go to: GitHub Issue Triggers (setting ID: githubIssues.createIssueTriggers) 1
  3. Click "Add item"
  4. Add - [ ] and - [ ] 2
  5. Click OK
  6. Confirm in "- [ ] " and "- [ ]" are added to the .json in your testing environment.

abbreviated

"githubIssues.createIssueTriggers": [
  "- [ ] ",
  "Specify requirements",
  "Plan",
  "- [ ]"
]
  1. Confirm other issue triggers are working.
  2. Test triggers "- [ ] " and "- [ ]" in markdown and html comment
 - [ ] Test task 
 - [ ]Test task
<!-- 
- [ ] Test task
- [ ]Test task
 -->

Footnotes

  1. Settings applies to all profiles. I also confirmed the .json in my workspace is up-to-date.

  2. Without a space at the end it is not working either.

@alexr00 alexr00 added the bug Issue identified by VS Code Team member as probable bug label May 27, 2024
@alexr00 alexr00 self-assigned this May 27, 2024
@alexr00 alexr00 added this to the June 2024 milestone May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants