You can do what @Peter said from the command line too!

Those commands remove all the sections of the git config file related to gitflow.

    git config --remove-section &quot;gitflow.path&quot;
    git config --remove-section &quot;gitflow.prefix&quot;
    git config --remove-section &quot;gitflow.branch&quot;

Then you can re-init gitflow as usual.

    git flow init



If you removed those sections from your config any reference to git-flow is gone.

There isn&#39;t really a need to remove anything though, the git-flow model is just that, it&#39;s a model. You can always use standard git commands.

What git-flow adds to your config, only git-flow software will use, not the git itself.

I&#39;m trying to figure out how to structure my application to use MySQL most efficent way. I&#39;m using node-mysql module. Other threads here suggested to use connection pooling so i set up a little module mysql.js

    var mysql = require(&#39;mysql&#39;);
    
    var pool  = mysql.createPool({
        host     : &#39;localhost&#39;,
        user     : &#39;root&#39;,
        password : &#39;root&#39;,
        database : &#39;guess&#39;
    });
    
    exports.pool = pool;

Now whenever I want to query mysql I require this module and then query the databse

    var mysql = require(&#39;../db/mysql&#39;).pool;
    
    var test = function(req, res) {
         mysql.getConnection(function(err, conn){
             conn.query(&quot;select * from users&quot;, function(err, rows) {
                  res.json(rows);
             })
         })
    }

Is this good approach? I couldn&#39;t really find too much examples of using mysql connections besides very simple one where everything is done in main app.js script so I don&#39;t really know what the convention / best practices are.

Should I always use connection.end() after each query? What if I forget about it somewhere?

How to rewrite the exports part of my mysql module to return just a connection so I don&#39;t have to write getConnection() every time?

node.js + mysql connection pooling

I&#39;d like find lines in files with an occurrence of some pattern and an absence of some other pattern. For example, I need find all files/lines including `loom` except ones with `gloom`. So, I can find `loom` with command:

    grep -n &#39;loom&#39; ~/projects/**/trunk/src/**/*.@(h|cpp)

Now, I want to search `loom` excluding `gloom`. However, both of following commands failed:

    grep -v &#39;gloom&#39; -n &#39;loom&#39; ~/projects/**/trunk/src/**/*.@(h|cpp)
    grep -n &#39;loom&#39; -v &#39;gloom&#39; ~/projects/**/trunk/src/**/*.@(h|cpp)

What should I do to achieve my goal?

***EDIT 1:*** I mean that `loom` and `gloom` are the character sequences (not necessarily the words). So, I need, for example, `bloomberg` in the command output and don&#39;t need `ungloomy`.

***EDIT 2:*** There is sample of my expectations.
Both of following lines are in command output:
&gt; I faced the icons that *loomed* through the veil of incense. 
&gt;
&gt; Arty is *slooming* in a *gloomy* day.

Both of following lines aren&#39;t in command output:
&gt; It’s *gloomyin’* ower terrible — great muckle doolders o’ cloods.
&gt;
&gt; In the south west round of the heigh pyntit hall


How to grep, excluding some patterns?

After `git flow init`, how to remove the git flow model?  
How do I remove all related config from the `.git/config` file?

&lt;!-- language: lang-sh --&gt;

    $ git flow init


&lt;!-- language: lang-sh --&gt;

    # force reset
    $ git flow init -f


How to remove below content from the `.git/config` file?
&lt;!-- language: lang-default --&gt;

    [gitflow &quot;branch&quot;]
        master = master
        develop = develop
    [gitflow &quot;prefix&quot;]
        feature = feature/
        release = release/
        hotfix = hotfix/
        support = support/
        versiontag = 


Is there a command to undo git flow init?

After <code>git flow init</code>, how to remove the git flow model? 
How do I remove all related config from the <code>.git/config</code> file?

<pre><code class="hljs language-csharp">$ git flow init
</code></pre>

<pre><code class="hljs language-csharp"># force reset
$ git flow init -f
</code></pre>
How to remove below content from the <code>.git/config</code> file?

<pre><code class="hljs language-ini">[gitflow "branch"]
 master = master
 develop = develop
[gitflow "prefix"]
 feature = feature/
 release = release/
 hotfix = hotfix/
 support = support/
 versiontag = 
</code></pre>

I have seen multiple contradicting definitions on various git flow related websites. Is there an official recommendation or single source of truth?

Branches: `release-1.2.3` or `release-v1.2.3`

Tags: `1.2.3` or `v1.2.3`

Git flow release branches and tags - with or without &quot;v&quot; prefix

Recently I started working on a big features, so I created a new ``feature/xyz`` branch. Problem is that this feature is big, so it will take me ~3 months to complete it. I would like to safely merge progress that has been made in ``develop`` to my feature branch, without worrying that changes from ``develop`` branch will override updates that I already made in my feature branch. My previous attempt to merge ``develop`` to ``feature/xyz`` ended up in some changes that I already made in the new feature being reverted.

What would be the command to achieve this? Thanks

GitFlow: safely merge develop changes to a feature branch

I am very new to Git and I am planning to contribute to some open-source project on GitHub after discovering a small error in it. Upon forking it and fixing the error, I purposed a pull request and I noticed this showing up:  

&gt; Failed — The Travis CI build failed

Looking into the details I discovered it was caused by `Could not find .travis.yml`, which made perfect sense since I had not signed in to Travis Cl with and add .travis.yml to the repository.

This is my first time hearing about Travis and what that is known as continuous integration. And it sounds pretty cool so in order to learn more about it, I looked it up on Wikipedia.


&gt;  Travis CI is a hosted, distributed continuous integration service
&gt; used to build and test projects hosted at GitHub. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to **build the project and run tests**. This includes commits to all branches, not just to the master branch.

My current understanding of Travis CI is that what it does is automatically pushing the project upon `git commit -am &quot;..&quot;` and I don&#39;t quite understand some part of it.

1. By **building the project and run tests**, what tests is it going to run? And how is it going to &quot;build&quot; the project? (like compiling it to binary?)

2. It states that &quot;This includes commits to all branches&quot; - but what if I don&#39;t want to commit to all branches?

3. Is it alright if I don&#39;t use Travis Cl at all? Under what circumstances is it best to use it (or it must be used)? 


Trying to understand what Travis CI does and when it should be used

I having been using `git flow` for a while now. I am curious to learn about a specific use case. 

For one of my projects I have a ticket for a new website feature. This ticket depends on many sub-tasks. I would like to create a feature branch for the main ticket, and then for each sub-task create a feature branch off of the parent feature branch.

Let&#39;s assume I have a ticket PROJ-500 and I create a feature branch for it

    git flow feature start PROJ-500

Then I want to integrate tickets `PROJ-501` through `PROJ-515` into `PROJ-500` before integrating the whole thing into `develop`. Is there a way for me to do something like

    git flow feature start PROJ-511 -b PROJ-500

Then over time these sub-tasks get completed and when their feature is finished, the branch is merged into `PROJ-500`. 

    git flow feature finish PROJ-511

The above command would merge `PROJ-511` into `PROJ-500`

And once all sub-tasks are completed then `PROJ-500` will be finished and merged into `develop`.

This way the new website feature is integrate into develop as a single unit rather than piecemeal. 

Git flow - create feature branch off another feature branch

We have a developer team of 4 and have recently moved to Git. We want to learn best practices regarding workflow with branching and merging. 

We are using a lightweight version of Git Flow. We have a dev, staging and a master branch which are all linear with each other. 

* staging is branched from master
* dev is branched from staging

On top of that we use feature and hotfix branches to work on new features and fix bugs. 

I have the following questions:

1. Should we branch feature branches from dev or from master?  
2. When a feature branch is ready, should we merge the feature branch into dev, then merge dev into staging, or merge the feature branch into staging and then the feature branch into master?

I think we should branch from master and merge the feature branch up, because there might be something in dev that we might not want to merge to staging and master.

What is your opinion? What are the best practices? 

Content Type	Original Author	Original Content on Stackoverflow
Question	payliu	View Question on Stackoverflow
Solution 1 - Git Flow	danidemi	View Answer on Stackoverflow
Solution 2 - Git Flow	Peter van der Does	View Answer on Stackoverflow

Is there a command to undo git flow init?

Git Flow Problem Overview

Git Flow Solutions

Solution 1 - Git Flow

Solution 2 - Git Flow

How to grep, excluding some patterns?

node.js + mysql connection pooling

Attributions