[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #DZC-590249]: Authorize github access
- Subject: [netCDF #DZC-590249]: Authorize github access
- Date: Fri, 02 Sep 2016 08:30:13 -0600
Hi,
Just a quick note; rather than add you to the official repository you will want
to first 'fork' the repository on GitHub. This will then let you make your
changes without having to worry about permissions. When you have code you want
to contribute back you will issue a pull request.
I hope this helps,
-Ward
Sent from my iPhone
> On Sep 1, 2016, at 9:42 PM, Dennis Heimbigner <address@hidden> wrote:
>
> New Staff Reply: Authorize github access
>
> Ok, lets get you started.
> 1. pick a directory into which you want to place the netcdf-c fork.
> I typically use a directory called 'git' (name is only a mnemonic).
> mkdir git
> 2. move to the git directory:
> cd git
> 3. The fork is created by executing this command in the 'git' (or whatever)
> directory
> git clone https://github.com/Unidata/netcdf-c.git
> [Note if you look at the netcdf-c home page on github
> (https://github.com/Unidata/netcdf-c), you should see
> a "clone or download" drop-down in the upper right.
> It will show the url to use with 'git clone'.]
> 4. Move into the netcdf-c directory
> cd netcdf-c
> 5. create a new branch for your changes:
> git branch newbranchname
> 6. move to the new branch
> git co newbranchname.
>
> This should get you started.
>
>
> =Dennis Heimbigner
> Unidata
>
>
> Ticket Details
> ===================
> Ticket ID: DZC-590249
> Department: Support netCDF
> Priority: Normal
> Status: Open
> Link:
> https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=27459
>
Ticket Details
===================
Ticket ID: DZC-590249
Department: Support netCDF
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.