Quantcast

git workflow notes on demo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

git workflow notes on demo

Eli Adam
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

James Klassen-2

https://github.com/geomoose/geomoose-utils/blob/master/update_to_master.sh

On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

James Klassen-2

I should note if you have local changes in a submodule, they need to be separately pushed before running this script.  Otherwise, the referenced commits won't be at github.

On Apr 10, 2015 5:53 PM, "James Klassen" <[hidden email]> wrote:

https://github.com/geomoose/geomoose-utils/blob/master/update_to_master.sh

On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

Eli Adam


On Fri, Apr 10, 2015 at 3:57 PM, James Klassen <[hidden email]> wrote:

I should note if you have local changes in a submodule, they need to be separately pushed before running this script.  Otherwise, the referenced commits won't be at github.


Ah, great, even better place for it.  I should have looked there first. 

Thanks, Eli

 
On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc


_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

James Klassen-2

It still could be documented better.   Like how to update a branch other than master, etc.

On Apr 10, 2015 7:01 PM, "Eli Adam" <[hidden email]> wrote:


On Fri, Apr 10, 2015 at 3:57 PM, James Klassen <[hidden email]> wrote:

I should note if you have local changes in a submodule, they need to be separately pushed before running this script.  Otherwise, the referenced commits won't be at github.


Ah, great, even better place for it.  I should have looked there first. 

Thanks, Eli

 
On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc


_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

Eli Adam
At some point we could discuss an alternate demo branch(es).  This would be another branch that we run another demo off of.  This could be especially useful for having people test issues in review.  A workflow like: fix the issue in master, config alt demo to be relevant to that fix, put issue into review and link to alt demo, then reporter can test the issue without figuring out how to run trunk.


Eli

On Fri, Apr 10, 2015 at 5:09 PM, James Klassen <[hidden email]> wrote:

It still could be documented better.   Like how to update a branch other than master, etc.

On Apr 10, 2015 7:01 PM, "Eli Adam" <[hidden email]> wrote:


On Fri, Apr 10, 2015 at 3:57 PM, James Klassen <[hidden email]> wrote:

I should note if you have local changes in a submodule, they need to be separately pushed before running this script.  Otherwise, the referenced commits won't be at github.


Ah, great, even better place for it.  I should have looked there first. 

Thanks, Eli

 
On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc



_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: git workflow notes on demo

James Klassen-2

That's sort of (but not completely) setup for other versions of the demo (similar to the docs).  Each branch has a lot of config before it auto updates.

Probably would be good to have a 2.x.whatever demo too (synced with the last official release instead of master).

On Apr 10, 2015 7:45 PM, "Eli Adam" <[hidden email]> wrote:
At some point we could discuss an alternate demo branch(es).  This would be another branch that we run another demo off of.  This could be especially useful for having people test issues in review.  A workflow like: fix the issue in master, config alt demo to be relevant to that fix, put issue into review and link to alt demo, then reporter can test the issue without figuring out how to run trunk.


Eli

On Fri, Apr 10, 2015 at 5:09 PM, James Klassen <[hidden email]> wrote:

It still could be documented better.   Like how to update a branch other than master, etc.

On Apr 10, 2015 7:01 PM, "Eli Adam" <[hidden email]> wrote:


On Fri, Apr 10, 2015 at 3:57 PM, James Klassen <[hidden email]> wrote:

I should note if you have local changes in a submodule, they need to be separately pushed before running this script.  Otherwise, the referenced commits won't be at github.


Ah, great, even better place for it.  I should have looked there first. 

Thanks, Eli

 
On Apr 10, 2015 4:34 PM, "Eli Adam" <[hidden email]> wrote:
Hi Jim,

You diligently keep the sub-modules in geomoose/geomoose/ updated so that the demo is reflective of the current commits.  Can you note the commands that you use to push these two commits?

https://github.com/geomoose/geomoose/commit/5f2c3b65717462aa822827efca90681d9898a121
https://github.com/geomoose/geomoose/commit/5955f838d6e60bc632b1e1847699b089191aa07f

I appreciate you keeping things current. 

Thanks, Eli

_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc



_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
Loading...