Forking otrunk-examples with git and using the fork for testing

[Stephen Bannasch]

I've put together some clear instructions for how to use git to fork
the otrunk-examples repository and make your own customizations or
entire new activities.

http://confluence.concord.org/display/CSP/Forking+otrunk-examples+with+git+and+using+the+fork+for+testing

This is useful for any developer you does not have commit rights to
CC's svn repository but wants to easily customize, experiment with,
or add-to the existing activities.

If you create changes or new code that you think should be combined
back into otrunk-examples send a message to the list.

[Stephen Bannasch]

>I've put together some clear instructions for how to use git to fork
>the otrunk-examples repository and make your own customizations or
>entire new activities.
>
>http://confluence.concord.org/display/CSP/Forking+otrunk-examples+with+git+and+using+the+fork+for+testing
>

Speaking with Chad yesterday it seemed that he and Aaron missed a
useful bit in step 12 in the documentation I created about how to get
access to the raw form of he resources without addeding additional
url query parameters.

12. Create a new External OTrunk Activity in a DIY instance and set
the External otml url to:

http://github.com/newgithubuser/otrunk-examples.git/LOOPS/hanging-with-friends-2-mw-jruby.otml

Note: the form of the url to get access to the raw files! Github only
makes plain http access to the raw forms of the files in the master
branch of the repository. The form of that url is:

http://github.com/<github-user>/<repository-name>.git/

Hmmm ... actually since I wrote that github was updated to support
real raw access to any resource in any branch:

http://support.github.com/discussions/feature-requests/3-clean-urls-for-raw-files-in-github-or-gist#comment_18252

Now it's easier and you can have raw access to any branch.

Here's an example:

This url renders an html view of the state of the
GENIQUEST-pilot-intro.otml file in HEAD revision of the master branch:

http://github.com/stepheneb/otrunk-examples/tree/master/Geniquest/GENIQUEST-pilot-intro.otml

This is the new form for access to the raw resource:

http://github.com/stepheneb/otrunk-examples/raw/master/Geniquest/GENIQUEST-pilot-intro.otml

When you are viewing an html representation of a resource on github
the "Raw" link references a url that presents the raw form of the
resource with any additional url query parameters.

I've upodated the confluence page:

http://confluence.concord.org/display/CSP/Forking+otrunk-examples+with+git+and+using+the+fork+for+testing

FYI: The jgit/egit Eclipse plugin is now quite functional. The update site is:

http://www.jgit.org/update-site/

Here's an intro for using github with Eclipse:

ttp://github.com/guides/using-the-egit-eclipse-plugin-with-github

[Chad]

Thanks for the update. I think Aaron did know this, but was concerned
about internal references in the files for some reason. This shouldn't
normally be a problem, but I wouldn't be surprised if there were links
in the GENIQUEST pilot files that made this a concern at the time. In
general, this is great news, and should make managing things through
Git just that much easier.

--Chad

On Dec 10, 1:38 pm, Stephen Bannasch <stephen.banna...@deanbrook.org>
wrote:

> >I've put together some clear instructions for how to use git to fork
> >the otrunk-examples repository and make your own customizations or
> >entire new activities.
>

> >http://confluence.concord.org/display/CSP/Forking+otrunk-examples+wit...

>
> Speaking with Chad yesterday it seemed that he and Aaron missed a
> useful bit in step 12 in the documentation I created about how to get
> access to the raw form of he resources without addeding additional
> url query parameters.
>
> 12. Create a new External OTrunk Activity in a DIY instance and set
> the External otml url to:
>

> http://github.com/newgithubuser/otrunk-examples.git/LOOPS/hanging-wit...

>
> Note: the form of the url to get access to the raw files! Github only
> makes plain http access to the raw forms of the files in the master
> branch of the repository. The form of that url is:
>
>    http://github.com/<github-user>/<repository-name>.git/
>
> Hmmm ... actually since I wrote that github was updated to support
> real raw access to any resource in any branch:
>

> http://support.github.com/discussions/feature-requests/3-clean-urls-f...

>
> Now it's easier and you can have raw access to any branch.
>
> Here's an example:
>
> This url renders an html view of the state of the
> GENIQUEST-pilot-intro.otml file in HEAD revision of the master branch:
>

>  http://github.com/stepheneb/otrunk-examples/tree/master/Geniquest/GEN...

>
> This is the new form for access to the raw resource:
>

>  http://github.com/stepheneb/otrunk-examples/raw/master/Geniquest/GENI...

>
> When you are viewing an html representation of a resource on github
> the "Raw" link references a url that presents the raw form of the
> resource with any additional url query parameters.
>
> I've upodated the confluence page:
>

> http://confluence.concord.org/display/CSP/Forking+otrunk-examples+wit...

[Aaron Unger]

Actually, I hadn't learned that trick until now, which is too bad
because that's exactly what we could have used for the pilot earlier.
Now we know. :-)

The earlier problem with referencing them directly is that via the
normal web ui for github, you have to add '?raw=true' to each url in
order to access the real file, and since there are embedded urls in
all of the otml's, they'd point to the github page, and not the real
file. But with the /raw/master url format, we can avoid that problem.

Thanks Stephen!

-- Aaron