Allow for issues to be manually refreshed
See original GitHub issueDescription
When creating issues on GitHub while GitHub Desktop is open, they won’t show up when referencing them in commit field (#issue-number
).
Version
GitHub Desktop version: 1.0.13
OS version: Microsoft Windows [Version 10.0.16299.248]
Steps to Reproduce
- Open GitHub Desktop
- Create an issue on GitHub
- GitHub Desktop fails to show it when referencing the issue in commit field.
Expected behavior: Being able to select the issue that was recently created.
Actual behavior: Fails to show the issue.
Reproduces how often: 100%
Logs
Additional Information
No additional information 😜
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Solved: Manual Refresh is Required After Changing the Stat...
Solved: I noticed that after changing the status of the issue to done, the result will not automatically reflect on the browser by...
Read more >Automatically refresh linked data types - Microsoft Support
Once set, you can refresh manually in a few different ways: Select Refresh All under the Data tab. Right-click a cell with a...
Read more >How to give the end user access to refresh on power bi web
Hi I am trying to create a provision where the end user can refresh the data source using a button may be on...
Read more >Power BI Refresh Trick – Data Refresh Issues - YouTube
Data refresh issues can be common in Power BI for new report developers. ... contains duplicate values and this is not allowed in...
Read more >Problem manually refreshing data from Google Sheets
Yesterday I encountered an issue where I pressed "Request Data Refresh" and received an error message stating "There was a problem refreshing the...
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
Shouldn’t we keep this open to track updating the issues when the user manually clicks “Fetch?”
Thanks for clarifying, closing this issue.