-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
TST: Standardize GitHub references #55461
Comments
I would prefer the URL reference moving forward |
not a huge deal but URL-based is awkward in a few cases where i want to grep: 1) for that said, the upside of standardizing outweighs those complaints so i wont object if thats what people prefer. |
I prefer short |
I would also vote for short. Probably |
If we go on votes alone, it's currently 6-to-3 in favor of URL. Not necessarily a large number of votes yet though, if you would like to abstain it would be helpful indicate that so we can get an idea of participation. |
agreed |
No preference |
It might be an obvious advantage of URLs, but to explicitly state why I prefer URLs: it allows me to simply click on it in my IDE to go to the issue (no need to copy paste the number, and then manually construct the url adding the number) And actually also for adding it in the code, I typically copy paste it from the issue web page, and then copying the whole url instead of only selecting the number of the url or from the title isn't any harder (or maybe even easier) (and if we go for short, I would prefer |
No preference, but +1 for consistency |
+1 |
This fell off my radar for a bit, but I'd like to pick it back up. We have 7 for URLs and 4 for a shortened form of some sort. If the short voters do not have objections, in a few weeks I'm going to start working on conforming the tests to URL - ideally with some form of pre-commit check. |
Mild preference for URLs |
Currently in tests we have a number of different formats for referencing GitHub issues or pull requests. The sense I gather is that there are two different formats people may like:
Short:
URL:
Please feel free to suggest any other alternatives as well. One option is of course to continue with the status-quo: no standardization of referencing GitHub issues.
cc @pandas-dev/pandas-core
The text was updated successfully, but these errors were encountered: