Skip to Content

WSG and Github Usage

Printer-friendly versionPrinter-friendly version

As of 04-23-2015 the UCSB Web Standards Group has a github organization presence at

The ucsb-wsg is an Open Source organization allowing it to have no hosting cost fees. All subprojects must also be open source to be listed here (and Public repositories).

Initially the organization has associated with it a repository for the UCSB webguide whose legacy URL is/was upon github repository creation.

Organization, Repository Management between Co-Chairs

The github organization was created by David Gurba on 04-23-2015. Upon co-chairs vacating their position at the WSG group they must pass-on Ownership of the organization to the current WSG co-chairs.

We invision the single ucsb-wsg organization eventually containing multiple subprojects. Co-Chairs may easily create child repositories after being affiliated with the Organization through their github user profile. To create new empty repositories for projects or Pages simply:

  • For Pages simply follow these directions:   (follow directions for "Organizations")
  • for code repositories create a repository whose owner is "ucsb-wsg" and then your repository name from

Accepting Work/Changes from UCSB staff and the public

Changes to the webguide or project should be done on a Fork / Pull workflow. Only the co-chairs have access to accept changes requested on a repository.

If you simply want to suggest a change to the web guide, you only need to do the following:

  1. Create a new issue describing the change (

This issue can be used to discuss the change and track work on the proposed change. Feel free to comment on other issues as well.

To actually make a change to the web guide

  1. Create a new issue describing the change (
  2. Create a fork of the Web Guide repo (
  3. On your own fork, create a branch with a name that references the issue (e.g. "responsive-redesign" or "broken-link-fix")
  4. Do all of the work associated with the change on this branch
  5. When you are finished, create a pull request from your branch to the master branch of the Web Guide Repo
    • Reference the issue number in the pull request title or description (e.g. "fixes #33")
  6. A Co-Chair will accept the pull request

Make sure to keep your fork and the branches on your fork in sync with the Web Guide repo by continuously pulling in changes from the master branch of the main repo. This will ensure you can make cleaner merges and pull requests with few conflicts.