Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DOC: Change remote name to upstream
See original GitHub issueThere were some discussions on astropy/astropy-project#151 regarding usage of origin vs upstream (vs astropy) as remote name in examples. As @taldcroft pointed out at https://github.com/astropy/astropy-project/issues/151#issuecomment-795924703 and https://github.com/astropy/astropy-project/issues/151#issuecomment-795927271 , upstream is the most widely used term, so perhaps it is less confusing if we update our dev docs to use upstream.
Example doc (one of many) that is affected: docs/development/workflow/git_edit_workflow_examples.rst
@embray , perhaps this can be part of your campaign to improve the dev docs?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have some plans for redoing a mass cleanup of the dev docs. The Numpy one is clearly worth learning from, and adapting slightly to Astropy.
And yes, I definitely prefer “upstream”.