Skip to content

History / Getting started with CTSM in git

Revisions

  • Fix link

    @billsacks billsacks committed Oct 2, 2019
    935f556

  • Add link from old page to new one In case there were links to the old page

    @billsacks billsacks committed Oct 2, 2019
    c848bc7

  • Rename page Danica suggested this rename as being more intuitive as the place to look for git development help.

    @billsacks billsacks committed Oct 2, 2019
    2e1056c

  • Fix a few more lowercase ctsm references for consistency

    @billsacks billsacks committed Oct 2, 2019
    08ed9d6

  • Change ESCOMP/ctsm to ESCOMP/CTSM Now that we have renamed the repo to ESCOMP/CTSM Most or all of these changes shouldn't be necessary, but it keeps things more self-consistent.

    @billsacks billsacks committed Oct 2, 2019
    77f2168

  • Add another git reference

    @billsacks billsacks committed Jul 8, 2019
    67b9711

  • Point to tutorial

    @billsacks billsacks committed Nov 7, 2018
    0515d1e

  • Add a section on incorporating changes in your pull request This part of the process has been unclear to people

    @billsacks billsacks committed Jun 28, 2018
    465a03b

  • Minor fix

    @billsacks billsacks committed Jun 22, 2018
    02c37f9

  • Add some materials for learning git Also: Stop duplicating information between the "Getting started" page and the "Recommended git setup" page.

    @billsacks billsacks committed Jun 22, 2018
    dd21381

  • Remove unused footnote reference

    @billsacks billsacks committed Apr 19, 2018
    8ef9cfa

  • Rewrite basic development workflow I have rewritten this to more clearly document a workflow that involves having a separate clone for each branch, since I think this is what people will typically want, at least when getting started.

    @billsacks billsacks committed Apr 19, 2018
    3daea71

  • Add --no-track Without this, your local branch tracks master, which isn't what you typically want

    @billsacks billsacks committed Apr 16, 2018
    d757b31

  • Point to software carpentry's git tutorial

    @billsacks billsacks committed Feb 6, 2018
    2efd3a2

  • Fix footnotes

    @billsacks billsacks committed Feb 6, 2018
    ea7fa64

  • Updated Getting started with CTSM in git (rest)

    @ekluzek ekluzek committed Feb 5, 2018
    4f6b77e

  • Add note about forks being public

    @billsacks billsacks committed Feb 4, 2018
    54c5cc8

  • minor edits

    @billsacks billsacks committed Feb 3, 2018
    20ecab1

  • add a footnote, and use auto-numbering for footnotes

    @billsacks billsacks committed Feb 3, 2018
    e785391

  • Remove some now-redundant information from development workflow; add a heading

    @billsacks billsacks committed Feb 3, 2018
    fad6802

  • Enter information on submitting a pull request

    @billsacks billsacks committed Feb 3, 2018
    b483158

  • more work on getting started guide

    @billsacks billsacks committed Feb 2, 2018
    5e1c1b8

  • Move footnotes to bottom of section

    @billsacks billsacks committed Feb 2, 2018
    44ae968

  • minor edits

    @billsacks billsacks committed Feb 2, 2018
    c42a053

  • more work on getting started guide

    @billsacks billsacks committed Feb 2, 2018
    0407c56

  • more work on getting started guide

    @billsacks billsacks committed Feb 2, 2018
    125d033

  • add some text

    @billsacks billsacks committed Feb 2, 2018
    b86a5ce

  • work on getting started

    @billsacks billsacks committed Feb 2, 2018
    9c5e9d4

  • don't try to use warning box after all: github doesn't render it

    @billsacks billsacks committed Feb 2, 2018
    b10d13b

  • add warning box, add a bit more

    @billsacks billsacks committed Feb 2, 2018
    534d02a