drphilmarshall / gettingstarted Goto Github PK

I could add notes on how to:

• Use the pipelines
• Make and use Epics #24
• Estimate complexity and make burndown charts #23

Some joker has pushed a whole bunch of ridiculous edits. Now we need to fix them.

• "Wiki" is mis-spelled
• Some lines have been given heading status with a '#'

Explain deadlines, all issues must have milestones, re-assigning, how ZenHub uses them in burndown charts

In two places, looks like.

Suggest we replace tipety top with "back to top."

I made a bunch of shortcut links to particular parts of the video tutorial at https://www.youtube.com/watch?v=2g9lsbJBPEs in the "show more" section of the information section under the video. Great if people can fork this repo, add some of these as hyperlinks from the relevant GettingStarted FAQ, and then submit your modifications as pull requests! Thanks :-)

Answer: first capture the commit (by starting the branch you wish you'd been on, or cheking out the right branch and cherry-picking the commit(s)). Then go back and clean up the wrong branch with git revert.

Switch hyperlinks to markdown []().

I'm going to write a new FAQ in response to the question by @stevechesley #8 - comments welcome!

As suggested by @cwwalter - some tips for enraged SVN users forced to use git. Thanks for getting this started, Chris!

Filter by assignee, milestone, label. Sort by recently updated. Providing links to filtered issues.

git add!

Travis CI (Continuous Integration) is a software engineering tool for automating the running of unit tests and show a [build passing] tag on GitHub repos to show the test coverage status. (This also let us to know who to blame when things break). Is there any possibility that @drphilmarshall will consider adding one of his wonderful tutorials for this? I meant to learn about this for a while and will be glad to help out.

Organizing sub-issues, labels to make parsing issue list easier. ZenHub epics vs homegrown GitHub epics

Document is basically un-navigable until then

Egad.

Hi there - I can help fix that :-)

This repo needs some example epics and milestones, for illustration.

Especially when editing both a fork and the base repo...

Ideas, all implementable with sed:

• Spelling mistakes
• Double words
• Formatting problems: [] -> () for example

Don't:

• Change spelling of git commands, or any technical terms, really