#26359: explain dual ticket tracking system
-------------------------------------+-------------------------------------
Reporter: beckastar | Owner:
Type: | kaifeldhoff
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by kaifeldhoff):
* owner: nobody => kaifeldhoff
* status: new => assigned
Comment:
What a about adding a paragraph about the role of GitHub at
[https://docs.djangoproject.com/en/1.9/internals/contributing/triaging-
tickets/#triage-workflow]
We could cover the following aspects:
- forking django in GitHub
- the git part of work at home
- create pull request in GitHub
- working with failing test
- working with merge-conflicts
- rebasing
I know that all this already exists in the docs, but my first experience
was, that the information about the complete GitHub-workflow is spread
over different sections. So in most cases a short description with a link
to a more spectific page should be sufficient. But I have to go through
this in detail.
--
Ticket URL: <https://code.djangoproject.com/ticket/26359#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.56914bcbc18843de1136ba68b4e75979%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
