Button links in global Pull requests / Issues pages are messed up
See original GitHub issueLinks to reproduce: Pull requests, Issues. Then click either the Commented
or Yours
button.
You can see in the screenshot that the href attributes of the original buttons (Created
, Assigned
, Mentioned
and Review requests
in the Pull requests page) don’t have a space (+
) after the archived:false
attribute.
This is what it loads if I press one of them:
And this is how it looks with the extension disabled:
I have version 19.4.7.1857 of the extension.
Great work on the project. Keep it up! 😃
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Linking a pull request to an issue - GitHub Docs
On GitHub.com, navigate to the main page of the repository. Under your repository name, click Issues. In the list of issues, click the...
Read more >Why is the Approve button disabled in GitHub "pull request ...
I solved it by going to "my-repo" > "my-branch" > "pull requests" > select my pull request > scroll down to the "Merge...
Read more >"You are not connected to a remote repository" - Visual Studio ...
When I open this repository in Visual Studio 2017 15.8.5, and in Team Explorer, I click on Pull Requests, I see "You are...
Read more >How To Link Pull Requests to Issues Using GitHub - Keypup
Option 1: Via the pull request title To link a Jira issue such as PROJ-123 or a GitHub issue such as my-org/my-project#475 to...
Read more >Checks for merging pull requests | Bitbucket Data Center and ...
It also helps to avoid the problem of code review blockages and the need to completely lock down a repository. Default merge checks....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is also happening with the current code given that the separators around the query are optional in the regex, given that it’s using
?
. I’ve put together a PR that fixes this as well: #1926.I finally wound up using split + filter + join to remove the query parameter, and it seems to be working well. Thanks for the guidance!
That’s how it was at some point but that also matches
user:bfred
inuser:bfred-it
when used after. The space is the right separator to use, but it shouldn’t also be dropped from both sides.