Is there a way to get the GitHub issues that were closed on-or-near a date? I have a commit in my codebase that does not reference an issue, and I'm wondering if it was done in response to a particular issue.
Ideally, I'd like to say "show me issues that were closed after August 10"
Use closed: to search for issues based on date closed. For example, to find issues closed after Aug 10, 2020, do
closed:>2020-08-10
You can also use a range. For example, to find issues closed in February or March of 2020, do:
closed:2020-02-01..2020-03-31
On the other hand, using state:closed updated:>=YYYY-MM-DD returns all issues that are currently closed and have been updated anytime on or after a particular date, which is not necessarily the same thing.
See the GitHub doc sections on the "closed" qualifier and working with dates.
Have a look at GitHub Searching issues and pull requests
.
An example would be something like:
state:closed updated:>=2013-02-01
with the date format as described in the docs as updated:YYYY-MM-DD
Related
I would like to view all of the GitHub issues opened during a specific time range for a single repository. For example, all issues opened during the month of December 2022.
I can query for issues created after a specific date with the following query: is:issue created:>2022-12-01, however attempting to limit the search to exclude issues opened after December 31st is not currently working for me. And I don't immediately see the syntax in the GitHub documentation [1].
[1] https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests
You need to use the range operator for these searches (which is ..):
is:issue is:open created:2022-01-01..2022-12-31 .
See the docs here: https://docs.github.com/en/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates
This question already has answers here:
How to compare two tags with git?
(5 answers)
Closed 2 years ago.
I have two versions of code with the old one named "CMSSW_11_2_0_pre3" and new one named "CMSSW_11_2_0_pre5". There is a difference of about 170 pull requests with about 500 commits between the two. Please see this link:
https://github.com/cms-sw/cmssw/releases/CMSSW_11_2_0_pre5
I want to list all the 500 commit ids into a txt file. Doing it manually by copying and pasting each id from the website itself will take lot of time. Is there any other way to do it?
Pretty easy actually:
git log --pretty=format:"%H" CMSSW_11_2_0_pre3..CMSSW_11_2_0_pre5 > file
Looking at the attached pic the last commit was 5 days ago, however the first 2 lines show changes 39 mins ago.
https://github.com/popcornmix/xbmc/tree/newclock5
If I click on the change description for the first line then it shows the commit was 3 year ago.
What am I missing here? Am I not understanding the whole commit/date/time thing?
Would appreciate it if someone explained this. I would think the latest commit should then show 39 mins ago?
On git are two types of dates: GIT_AUTHOR_DATE (when you made the original commit) and GIT_COMMITTER_DATE (when patch was applied).
In your example changes was commited 3 years ago but was applied later.
You could read more about author and commiter differences here: https://stackoverflow.com/a/18754896/1349549
I am not sure if this is possible - I would like to know which issues were in which state on certain date. I tried but did not find anything. Any help would be appreciated.
EDIT: To make it clear, I would like to see status of the project e.g. a week ago, such as:
PROJECT=A AND issueType=Bug ON 2015/04/04 //something like that
Yes you can !!
Jira has advanced search feature,where you can provide different query and you can also get all bugs for one or more projects at particular data.
For more details go through
To get bugs created,resolved or updated on particular date there are custom fields created at , resolved at and updated at and then you need pass date in yyyy-mm-dd format
[Reference] http://blogs.atlassian.com/2013/01/jql-the-most-flexible-way-to-search-jira-14/
Is the order of repositories for a user simply the order of entry? I cannot see any logic in what is at the top of, for example, thoughtbot.
I'm thinking of writing a tool to get my desired ordering using the API, but maybe if I grokked the order better I could scan the list easier and not feel so compelled.
For example, as of 2013-12-21 16:01, these are the top two items on Thoughtbot:
shoulda-matchers - Last updated a day ago
suspenders - Last updated a day ago
But then the top item does not say it was updated a day ago ;
Dec 18, 2013 - Make order option Rails 4.0.1-compatible - aff7bd7e2a - authored 20 days ago
And the second on the list says it was authored a day ago
Dec 20, 2013 - Add spring - 078237f9ed - authored a day ago
Update;
The pull request is not related to the dates, see below. The comments are not related either. Thus I conclude perhaps there is evidence of a github bug. I will send another note to them. Perhaps this detail will help!
The two Closed Pull requests as of 2013-12-30Mon.09:19:09
TOP item = 11d ago ;
https://github.com/thoughtbot/shoulda-matchers/pulls?direction=desc&page=1&sort=created&state=closed
Make order option Rails 4.0.1-compatible
This is a fix for #388. From the commit: The way that we figure out whether the value which is p…
by mcmire 11 days ago
3 comments
2ND ITEM
https://github.com/thoughtbot/suspenders/pulls?direction=desc&page=1&sort=created&state=closed
Add spring
It's good stuff, and Rails 4.1 will include Spring by default. We may as well get on this train e…
by jferris 10 days ago
1 comment
They're ordered by time of last commit, newest at the top.
If you have a look at the GitHub API it says that the repositories are ordered by their creation date. Github API for listing repositories
It seems that this is also the case if for your personal repositories in the repository view. (Just tested this on my account)
(EDIT: I just realized that for the account that you mentioned, the repos are ordered by their last commit. However this is not the case for my account. It seems that the ordering depends on the overall number of repos linked to the account)