Re: [git-users] Git Newbie

[Michael]

On 2020-01-15, at 9:19 AM, Subbu Subbu  wrote:

> How do you select the build software after doing a fork of your source in 
> github. How can multiple developers use github.

Github is an entirely different beast than git.

There may be people on this list that can help you, but that's a different 
question than just "Here's the book that documents git".

Github, gitlab, bitbucket, are the three biggest websites that let you host git 
repositories.
All of them behave at least a little differently.

> 
> Regds
> Subbu

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/93A9BF5F-9C9E-4D9E-B9D1-C5C2E1DFF1CE%40gmail.com.

Re: [git-users] Git Newbie

[Michael]

On 2020-01-15, at 9:19 AM, Subbu Subbu  wrote:

> How do you select the build software after doing a fork of your source in 
> github. How can multiple developers use github.

Can you please clarify what you'd like to find out? 

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/2F163AFA-ED52-400C-BF6A-09716166B2DF%40gmail.com.

Re: [git-users] Git Newbie

[Marty McGowan]

Big open-ended questions. I'm sure you'll find this helpful:

https://git-scm.com/book/en/v2

=*+[]+ Marty McGowan 908 230-3739
64 Diamond Spring Dr, Monroe Twp NJ 08831
http://mcgowans.org/pubs/family




On Wed, Jan 15, 2020, at 11:19, Subbu Subbu wrote:
> How do you select the build software after doing a fork of your source in 
> github. How can multiple developers use github.
> 
> Regds
> Subbu
> 

> --
> You received this message because you are subscribed to the Google Groups 
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to git-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/git-users/d3e9ff78-0047-4380-a85f-71e5ee3da464%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/c33519a1-a586-42c5-8bbf-43f4a4654760%40www.fastmail.com.

[git-users] Git Newbie

[Subbu Subbu]

How do you select the build software after doing a fork of your source in 
github. How can multiple developers use github.

Regds
Subbu

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/d3e9ff78-0047-4380-a85f-71e5ee3da464%40googlegroups.com.

[git-users] Git newbie questions

[Ron K Jeffries]

I'm aware of git, but have not used it myself. Now I want to set up a 
static blog site on AWS S3, using [TBD tool, Jekyll seems promising...] to 
pump out the HTML etc.

My preference would be a Git workflow that accommodates my heavy (but not 
exclusive) use of ChromeOS. That implies (I think...) that instead of 
having a local git repository, my git would live in the cloud somewhere.
 
Advice please. I need to get my act together and DO this rather than THINK 
ABOUT doing it. LOL

ron k jeffries 805-567-4670 mobile

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [git-users] Git newbie trying to form a development workflow

[Cahyadi Hendrawan]

Hi William,





 Would you simply revert master back to known working state and merge the
 feature branch back in at a later date when its fixed and working?
 (Wondering if doing something like that messes with the history and causes
 problems down the line when merging feature branches into master?)

 If the changes made in a branch are not big, the merge will probably be
 simple. However, it can be a mess if the feature branch took a long time to
 be done. So, I think that the best way is to divide the feature in small
 tasks that don't take a long time to be completed and merged in the main
 branch.


We are also trying to implement branch per task workflow in our company. To
do a feature X, we divide the feature into several small task that can be
done by several people. It is often that the task are depends on other
task, so we often have a situation where certain people need to wait for a
task to be merged into master before they can start their work. The task
that the other tasks depend on is probably has been (functionally)
finished, but still pending for approval due to code-review, sanity check,
etc.

This become a major problem for us. How do you handle such scenario?

Regards,
Chen

-- 

Re: [git-users] Git newbie trying to form a development workflow

[Bryan Migliorisi]

I've been reading about git-flow and doing some experiments, and though I 
am no expert with it yet, I think its a good tool for these types of 
scenarios.  I have not tried this with the team yet but my idea would be to 
use git-flow to create a feature branch locally and push that branch up to 
the origin so that other people can work on that branch.  And when all the 
work is complete, git-flow will merge it back into the development branch 
and eventually into master, for deployment.



On Sunday, December 16, 2012 10:34:59 PM UTC-5, Chen Hendrawan wrote:

 Hi William,

  

   

 Would you simply revert master back to known working state and merge the 
 feature branch back in at a later date when its fixed and working? 
 (Wondering if doing something like that messes with the history and causes 
 problems down the line when merging feature branches into master?)

 If the changes made in a branch are not big, the merge will probably be 
 simple. However, it can be a mess if the feature branch took a long time to 
 be done. So, I think that the best way is to divide the feature in small 
 tasks that don't take a long time to be completed and merged in the main 
 branch.


 We are also trying to implement branch per task workflow in our company. 
 To do a feature X, we divide the feature into several small task that can 
 be done by several people. It is often that the task are depends on other 
 task, so we often have a situation where certain people need to wait for a 
 task to be merged into master before they can start their work. The task 
 that the other tasks depend on is probably has been (functionally) 
 finished, but still pending for approval due to code-review, sanity check, 
 etc. 

 This become a major problem for us. How do you handle such scenario?

 Regards,
 Chen


-- 

Re: [git-users] Git newbie trying to form a development workflow

[William Mizuta]

Hello Chen,

it is really a big problem when we have tasks that depends on other tasks.
To avoid this, our PO try to select tasks that don't depend on each other
per iteration. In the next iteration, if the task is done (it includes
code-review, test...), the PO selects a task that depends on already done
tasks.

However, sometimes it's not possible to do. In these cases, I think that
the best solution is to define the api of the tasks and create a branch for
each one. You don't need to know how the task will be done
(implementation), but you know what the task will do (api) and use it in
other tasks. This way, we can start a task B that depends on a task A even
if A is not done yet. After A is completed, we can merge the branch A into
branch B and finish the task B.


William Seiti Mizuta
@williammizuta
Desenvolvedor da Caelum



On Mon, Dec 17, 2012 at 1:34 AM, Cahyadi Hendrawan chen.hendra...@gmail.com
 wrote:

 Hi William,





 Would you simply revert master back to known working state and merge the
 feature branch back in at a later date when its fixed and working?
 (Wondering if doing something like that messes with the history and causes
 problems down the line when merging feature branches into master?)

 If the changes made in a branch are not big, the merge will probably be
 simple. However, it can be a mess if the feature branch took a long time to
 be done. So, I think that the best way is to divide the feature in small
 tasks that don't take a long time to be completed and merged in the main
 branch.


 We are also trying to implement branch per task workflow in our company.
 To do a feature X, we divide the feature into several small task that can
 be done by several people. It is often that the task are depends on other
 task, so we often have a situation where certain people need to wait for a
 task to be merged into master before they can start their work. The task
 that the other tasks depend on is probably has been (functionally)
 finished, but still pending for approval due to code-review, sanity check,
 etc.

 This become a major problem for us. How do you handle such scenario?

 Regards,
 Chen

 --




-- 

[git-users] Git newbie trying to form a development workflow

[Bryan Migliorisi]

Hey all,

Just learning Git and I am trying to understand the best workflow for our 
team.  For arguments sake, assume we are using Github for 
our private repositories and using Heroku for hosting.

I'd like to have a workflow where our development team commits changes to a 
development branch.  Someone (likely me) will be responsible for cherry 
picking commits from the development branch (or branches maybe?) and 
pulling them into a QA branch which is then pushed to our Heroku QA 
repository\app.

Once QAed and approved, I'd like to pull (merge?) the entire QA branch into 
the production branch and push that to our Heroku production repository.


Some questions:

   1. At a high level, does this make sense and is there a better way?  The 
   goal is mostly to allow concurrent development while allowing us to 
   selectively deploy specific changes.
   2. Is it best to have separate repositories for each developer and have 
   them push changes, once complete, to the main development repo? Or should 
   everyone just commit their code to the main development repo?
   3. Related to above: Should each developer have a separate branch or a 
   separate repository?
   4. Are there any tools to facilitate a workflow like this? Obviously 
   command line is immensely powerful.  Ive been using SourceTree 
   and liking it so far.  Also hear Tower is great. GitHub for Mac(\Windows) 
   is pretty limiting.

I've read a few blogs\articles describing some workflows similar to this 
but I havent really been able to wrap my head around it entirely.  Any 
links would be appreciated.

Thanks in advance!


-- 

Re: [git-users] Git newbie trying to form a development workflow

[William Mizuta]

Hey Bryan,

in my current project, we use feature branch to do our tasks, i.e. for each
task we create a new branch in the main repository and everyone can commit
in this branch. Once the task is completed and approved, we merge the
branch into the main (master) and delete this branch. With this workflow,
everyone can continue a job that someone stopped and the main branch
contains only approved features.

Another way that I know that can help you is pull request. Every member of
the team fork the main project and work on his fork. Once the task is
completed, he can ask for a pull request in the main project, which can be
approved or declined before it is merged in the main project. I don't like
this way of work because each member can ask only one pull request at time.
This way, the member can't start a new task before his pull request was
approved.

Hope that helped you


William Seiti Mizuta
@williammizuta
Desenvolvedor da Caelum



On Wed, Dec 12, 2012 at 1:44 PM, Bryan Migliorisi br...@migliorisi.comwrote:

 Hey all,

 Just learning Git and I am trying to understand the best workflow for our
 team.  For arguments sake, assume we are using Github for
 our private repositories and using Heroku for hosting.

 I'd like to have a workflow where our development team commits changes to
 a development branch.  Someone (likely me) will be responsible for cherry
 picking commits from the development branch (or branches maybe?) and
 pulling them into a QA branch which is then pushed to our Heroku QA
 repository\app.

 Once QAed and approved, I'd like to pull (merge?) the entire QA branch
 into the production branch and push that to our Heroku production
 repository.


 Some questions:

1. At a high level, does this make sense and is there a better way?
 The goal is mostly to allow concurrent development while allowing us to
selectively deploy specific changes.
2. Is it best to have separate repositories for each developer and
have them push changes, once complete, to the main development repo? Or
should everyone just commit their code to the main development repo?
3. Related to above: Should each developer have a separate branch or a
separate repository?
4. Are there any tools to facilitate a workflow like this? Obviously
command line is immensely powerful.  Ive been using SourceTree
and liking it so far.  Also hear Tower is great. GitHub for Mac(\Windows)
is pretty limiting.

 I've read a few blogs\articles describing some workflows similar to this
 but I havent really been able to wrap my head around it entirely.  Any
 links would be appreciated.

 Thanks in advance!


  --




-- 

Re: [git-users] Git newbie trying to form a development workflow

[Bryan Migliorisi]

Hi William.

Thanks for your reply. Havent thought much about bug fixes, but I suppose 
they could be done on master directly. Is that what youre doing on your 
current project?

Who is responsible for merging a feature branch with master? I'm guessing 
there are no restrictions.  I think that would be one difference from the 
forking method, since with forking, not everyone would have\need access to 
commit\push to the 'main' repo.

How would you handle a scenario where someone completes work on a feature 
branch, merges it into master and then finds that its broken?  Would you 
simply revert master back to known working state and merge the feature 
branch back in at a later date when its fixed and working? (Wondering if 
doing something like that messes with the history and causes problems down 
the line when merging feature branches into master?)


Thanks again,
Bryan

On Wednesday, December 12, 2012 11:00:05 AM UTC-5, William Mizuta wrote:

 Hey Bryan,

 in my current project, we use feature branch to do our tasks, i.e. for 
 each task we create a new branch in the main repository and everyone can 
 commit in this branch. Once the task is completed and approved, we merge 
 the branch into the main (master) and delete this branch. With this 
 workflow, everyone can continue a job that someone stopped and the main 
 branch contains only approved features.

 Another way that I know that can help you is pull request. Every member of 
 the team fork the main project and work on his fork. Once the task is 
 completed, he can ask for a pull request in the main project, which can be 
 approved or declined before it is merged in the main project. I don't like 
 this way of work because each member can ask only one pull request at time. 
 This way, the member can't start a new task before his pull request was 
 approved.

 Hope that helped you


 William Seiti Mizuta
 @williammizuta
 Desenvolvedor da Caelum



 On Wed, Dec 12, 2012 at 1:44 PM, Bryan Migliorisi 
 br...@migliorisi.comjavascript:
  wrote:

 Hey all,

 Just learning Git and I am trying to understand the best workflow for our 
 team.  For arguments sake, assume we are using Github for 
 our private repositories and using Heroku for hosting.
  
 I'd like to have a workflow where our development team commits changes to 
 a development branch.  Someone (likely me) will be responsible for cherry 
 picking commits from the development branch (or branches maybe?) and 
 pulling them into a QA branch which is then pushed to our Heroku QA 
 repository\app.

 Once QAed and approved, I'd like to pull (merge?) the entire QA branch 
 into the production branch and push that to our Heroku production 
 repository.


 Some questions:

1. At a high level, does this make sense and is there a better way? 
 The goal is mostly to allow concurrent development while allowing us to 
selectively deploy specific changes. 
2. Is it best to have separate repositories for each developer and 
have them push changes, once complete, to the main development repo? Or 
should everyone just commit their code to the main development repo? 
3. Related to above: Should each developer have a separate branch or 
a separate repository?
4. Are there any tools to facilitate a workflow like this? Obviously 
command line is immensely powerful.  Ive been using SourceTree 
and liking it so far.  Also hear Tower is great. GitHub for Mac(\Windows) 
is pretty limiting. 

 I've read a few blogs\articles describing some workflows similar to this 
 but I havent really been able to wrap my head around it entirely.  Any 
 links would be appreciated.

 Thanks in advance!


  -- 
  
  




-- 

[git-users] Git newbie not understanding branching and/or git flow

[John Green]

I'm transitioning from svn to git and I'm having a bit of a problem.
I'm using git flow and I can't bring down changes I made.

Here's what I've done. First,  I needed to get my svn sources down to
my laptop and init a git repository with them. (I don't mind losing my
svn history, really, I don't.) Step 1 was to create a git repository
on my hosting company's server using their web UI. Then I did the
following:

$ mkdir workspace
$ cd workspace/
$ svn export https://myCompany.myGitHost.com/myCompany/MyProject/trunk
MyProject
$ cd MyProject/
$ git init
$ git add .
$ git commit .
$ git push g...@mycompany.mygithost.com:myCompany/MyProject-Git.git
master

This all seemed to work fine, giving me all the usual git stuff. Now I
want to test this. Can I bring it down again (say I was another
engineer) and can I use git flow properly?

$ cd ../..
$ mkdir test
$ cd test
$ git clone g...@mycompany.mygithost.com:myCompany/MyProject-Git.git

It all looks good. I've brought my files down to my laptop.

$ cd MyProject-Git/
$ git flow init
$ git flow feature start addFoo

I make a mod, creating a file named foo in my source hierachy.

$ git add .
$ git commit
$ git flow feature finish addFoo
$ git push origin develop

Ok, now lets see if we can bring this down from the remote server  .

$ cd ../..
$ mkdir test2
$ cd test2
$ git clone g...@mycompany.mygithost.com:myCompany/MyProject-Git.git
$ cd MyProject-Git/
$ git flow init

I did the last git flow init just to make sure I was on the develop
branch, since that was where the new file was created.

My new file foo is not there. Where do I go wrong?

I appreciate any advice, I feel so close to having it!

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Git newbie not understanding branching and/or git flow

[Chris Stone]

You need to git checkout develop after you clone unless you specify the
branch during clone
On Oct 28, 2011 1:39 PM, John Green johngreen27...@gmail.com wrote:

 I'm transitioning from svn to git and I'm having a bit of a problem.
 I'm using git flow and I can't bring down changes I made.

 Here's what I've done. First,  I needed to get my svn sources down to
 my laptop and init a git repository with them. (I don't mind losing my
 svn history, really, I don't.) Step 1 was to create a git repository
 on my hosting company's server using their web UI. Then I did the
 following:

 $ mkdir workspace
 $ cd workspace/
 $ svn export https://myCompany.myGitHost.com/myCompany/MyProject/trunk
 MyProject
 $ cd MyProject/
 $ git init
 $ git add .
 $ git commit .
 $ git push g...@mycompany.mygithost.com:myCompany/MyProject-Git.git
 master

 This all seemed to work fine, giving me all the usual git stuff. Now I
 want to test this. Can I bring it down again (say I was another
 engineer) and can I use git flow properly?

 $ cd ../..
 $ mkdir test
 $ cd test
 $ git clone g...@mycompany.mygithost.com:myCompany/MyProject-Git.git

 It all looks good. I've brought my files down to my laptop.

 $ cd MyProject-Git/
 $ git flow init
 $ git flow feature start addFoo

 I make a mod, creating a file named foo in my source hierachy.

 $ git add .
 $ git commit
 $ git flow feature finish addFoo
 $ git push origin develop

 Ok, now lets see if we can bring this down from the remote server  .

 $ cd ../..
 $ mkdir test2
 $ cd test2
 $ git clone g...@mycompany.mygithost.com:myCompany/MyProject-Git.git
 $ cd MyProject-Git/
 $ git flow init

 I did the last git flow init just to make sure I was on the develop
 branch, since that was where the new file was created.

 My new file foo is not there. Where do I go wrong?

 I appreciate any advice, I feel so close to having it!

 --
 You received this message because you are subscribed to the Google Groups
 Git for human beings group.
 To post to this group, send email to git-users@googlegroups.com.
 To unsubscribe from this group, send email to
 git-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/git-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Git newbie not understanding branching and/or git flow

[John Green]

On Fri, Oct 28, 2011 at 3:43 PM, Chris Stone nightshade1...@gmail.comwrote:

 You need to git checkout develop after you clone unless you specify the
 branch during clone


Ok, I did miss that, but here's what happens.

$ git checkout develop
Already on 'develop'

Of course I can do  a checkout master and then a checkout develop and of
course the files don't change since I need to get them from the remote
machine. Some googling later I try this:

$  git checkout -b develop origin/develop
fatal: git checkout: branch develop already exists

Sigh...

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Git newbie not understanding branching and/or git flow

[John Green]

On Fri, Oct 28, 2011 at 4:48 PM, Chris Stone nightshade1...@gmail.comwrote:

 Sorry about the short reply earlier I was on my phone.
 What's going on here is when you did the clone it defaults to master. When
 you did git flow init it created the develop branch for you. To get your
 test file while on develop you need to perform a git merge origin/develop.
 If you did a fresh clone then the git checkout develop or origin/develop
 depending on how you have git configured would have worked. For more
 information I would check out the man pages for git clone git checkout and
 git merge. Not trying to say RTD here. I have found that git has a lot of
 options and the best way to find out which one you need is to look at the
 man pages. I hope this helps John.


Thanks Chris! I'll take a look at that on Monday. I had hoped the git flow
would have handled that for me. Guess not.

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.