GitHub 관련 문제에 대한 의견을 어떻게 추적합니까?
GitHub 에서 언급 한 모든 문제를 쉽게 찾고 싶습니다 .
검색 문제에 대한 GitHub 도움말commenter:mbigras type:issue
의 권장 사항에 따라 검색 을 시도했습니다 .
그러나이 방법은 내 프로필의 공개 활동 섹션보다 적은 결과를 반환합니다.
첨부 된 이미지를 모두보십시오 :
검색 방법
프로필 방법
GitHub에 대한 내 의견의 전체 역사를 얻을 수있는 방법이 있습니까?
편집하다
author:mbigras type:issue
더 넓은 결과를 제공하지만 여전히 전체 기록은 아닙니다.
내가 찾고있는 것은 모든 문제에 대한 내 의견 / 이슈 기록을 빠르게 볼 수있는 방법입니다.
편집하다
I emailed GitHub about this. Search doesn't match the public activity section because search indexes issues by creation date and not last active date.
How do you keep organized about which issues you've commented on?
Search for commenter:username
in the main Github
search box.
For example commenter:gavinandresen
To see recent activity, select Recently updated
from Sort dropdown
You can also narrow the search: is:issue commenter:gavinandresen
I have also been very frustrated when I could not find an issue that I have commented on a while ago. I even did not remember the project it was in. I knew only the problem I was referring to.
Then, I went to the Notification settings on Github and saw there is an Include your own updates option that is unchecked by default.
Once you check it, Github will send you an e-mail notification about every comment or PR you make. They you probably want to add an appropriate label and filter for emails so Github messages do not clutter an inbox.
My life has changed since then. Now, every time I want to find something I have written on Github, I just search for it in the e-mail notifications.
You can view all the issues on Github you have commented on by going to https://github.com/notifications/subscriptions and selecting Reason
as Comment
.
This will show all the issues that you've commented on.
You can also filter the issues by selecting other reason such as Assign
, Author
, Manual
, Mention
, etc. but you can select only one reason at a time. Also, you can filter the issues by repository by selecting the concerned repository from dropdown after clicking Repository
This might be a little late, but there's also another way to find what issues/PRs you have participated in. This method also brings in a lot more things you might be interested in too!
When you are on the website main page, on github.com, use the keyboard shortcuts as described here to open your pull requests or issues. The shortcut for these is in particular [g
, i
] for issues and [g
, p
] for pull requests (I remember g
by go, but whatever works for you.)
After you go to the page directed by these shortcuts you are greeted by an entire screen of goodies you can use! The search bar can be edited and the buttons can be used to make your experience fast!
Also, since Github is on the web, any HTTP search engine works, eg Google, Bing, etc. This works to the extent of your search engine's quality and the uniqueness of the writer name.
(Indeed, I actually do this all the time when I need to find any previously written web (engine)-accessible publication, including those on StackExchange. Names I use are 1 in probably an infinity, so Google often works better than forum search options.)
'development' 카테고리의 다른 글
Bash 스크립트에 전달 된 인수 수를 어떻게 찾습니까? (0) | 2020.05.29 |
---|---|
C # 코드에서 .NET 4.0 튜플을 사용하는 것이 좋지 않은 디자인 결정입니까? (0) | 2020.05.28 |
문자열을 올바르게 비교하려면 어떻게합니까? (0) | 2020.05.28 |
Angular 프로젝트에서 부트 스트랩을 사용하는 방법은 무엇입니까? (0) | 2020.05.28 |
다양한 캐시 및 메인 메모리에 액세스하는 데 드는 대략적인 비용은? (0) | 2020.05.28 |