Top Banner
This session will be recorded
42

Github introduction for W3C WCAG WG and EOWG

Jan 22, 2018

Download

Education

Eric Eggert
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Github introduction for W3C WCAG WG and EOWG

This session will be recorded

Page 2: Github introduction for W3C WCAG WG and EOWG

Git & GithubGit & GithubAn introduction

Eric Eggert

W3C/WAI

[email protected]

w3.org/People/Yatil

Page 3: Github introduction for W3C WCAG WG and EOWG

NoteNoteDifferent editors have different

preferences for using Github.Please talk to the editor of the

delivery you want to contribute to.

Page 4: Github introduction for W3C WCAG WG and EOWG

ContributionsContributionswelcome!welcome!

Page 5: Github introduction for W3C WCAG WG and EOWG

GitGit„Git is a distributed revision

control system with an emphasis onspeed, data integrity, and support

for distributed, non-linearworkflows.“

Page 6: Github introduction for W3C WCAG WG and EOWG

http://www.git-tower.com/learn/git/ebook/command-line/basics/what-is-version-control

Page 7: Github introduction for W3C WCAG WG and EOWG

RepositoryRepositoryStores all versions and

associated metadata for theproject

Page 8: Github introduction for W3C WCAG WG and EOWG

Local & RemoteLocal & RemoteRepositoriesRepositories

In Git, every computer has acomplete copy of the repository

(Local Repositories)

All changes can then be synced to acentral remote repository

Page 9: Github introduction for W3C WCAG WG and EOWG

CommitCommitA Commit is a specific set of

changes that is submitted to therepository, creating a new version

(of the committed files)

each commit has a “commit message”that describes what was archived

with this commit

Page 10: Github introduction for W3C WCAG WG and EOWG

BranchesBranches

Page 11: Github introduction for W3C WCAG WG and EOWG

BranchesBranches1. Easy to create2. helps to concentrate on one change3. can later be merged into the “main” branch4. avoids collisions from multiple editors

Page 12: Github introduction for W3C WCAG WG and EOWG
Page 13: Github introduction for W3C WCAG WG and EOWG

no need for CLIno need for CLI

Page 14: Github introduction for W3C WCAG WG and EOWG

Source treeSource treeMac & Windows

Page 15: Github introduction for W3C WCAG WG and EOWG

Github for WindowsGithub for WindowsWindows

Page 16: Github introduction for W3C WCAG WG and EOWG

Github for MacGithub for MacMac

Page 17: Github introduction for W3C WCAG WG and EOWG

GithubGithub

Page 18: Github introduction for W3C WCAG WG and EOWG

A GUI for A GUI for RemoteRemote Repositories Repositories

Cprovides other project management helpers,

such as:

Issue management

Wiki

Milestones

Page 19: Github introduction for W3C WCAG WG and EOWG

Each delivery has its ownEach delivery has its ownrepositoryrepository

For example:

github.com/w3c/wai-tutorials/github.com/w3c/wai-quick-start/github.com/w3c/wai-wcag-quickref/

Page 20: Github introduction for W3C WCAG WG and EOWG

Edit FilesEdit Files

Github GithubO

Page 22: Github introduction for W3C WCAG WG and EOWG

All kinds of file typesAll kinds of file types

HTMLCSS/SASS/…JavaScriptPHP/Ruby/Python/…Markdown(Also w/ YAML FRONTMATTER)

Page 23: Github introduction for W3C WCAG WG and EOWG

ISSUESISSUES

Page 25: Github introduction for W3C WCAG WG and EOWG

PullPullrequestsrequests

Page 27: Github introduction for W3C WCAG WG and EOWG

Reference syntaxReference syntax

@username – notifies a user about a comment(Pretty much like @-replies on Twitter)#123 – References that issue6f8bddc011 – references that commit

Page 28: Github introduction for W3C WCAG WG and EOWG

Github flavored MarkdownGithub flavored Markdown

Page 29: Github introduction for W3C WCAG WG and EOWG

When to useWhen to usewhat?!what?!

Page 30: Github introduction for W3C WCAG WG and EOWG

IssuesIssuesGeneral feedbackDiscussing passages of documentscollecting opinions

Page 31: Github introduction for W3C WCAG WG and EOWG

Writing Writing “good” “good” IssuesIssues

Page 32: Github introduction for W3C WCAG WG and EOWG

Always provide a link to the pageAlways provide a link to the pagein questionin question

Or, if possible, a link to the section of the page

Page 33: Github introduction for W3C WCAG WG and EOWG

Keep the issue clear, concise andKeep the issue clear, concise andfocused on a specific issuefocused on a specific issue

Page 34: Github introduction for W3C WCAG WG and EOWG

Bad: “I don’t like content of page X”Bad: “I don’t like content of page X”

good: “On page X the wording in thegood: “On page X the wording in theintroduction is unclear.”introduction is unclear.”

Page 35: Github introduction for W3C WCAG WG and EOWG

Pull requestsPull requestsConcrete text/code proposalsimplementing changes that have already beendiscussedTypos & grammar corrections

Page 36: Github introduction for W3C WCAG WG and EOWG

creating creating “good” “good”

pull requestspull requests

Page 37: Github introduction for W3C WCAG WG and EOWG

Make “atomar” changesMake “atomar” changes

If there are multiple, independent wordingchanges, create multiple pull requestsif it’s a change throughout a page (or repository),one pull request is enough

Page 38: Github introduction for W3C WCAG WG and EOWG

Github workflowGithub workflow

Create branch

Page 39: Github introduction for W3C WCAG WG and EOWG

Github workflowGithub workflow

Commit changes

Page 40: Github introduction for W3C WCAG WG and EOWG

Github workflowGithub workflow

Open a pull request

Page 41: Github introduction for W3C WCAG WG and EOWG

Github workflowGithub workflow

Discuss and (optionally) add more commits

Page 42: Github introduction for W3C WCAG WG and EOWG

Github workflowGithub workflow

Merge