Well, basically it is a matter of preference, but I prefer the version with the `v`, as [Semver](http://semver.org/) does it [that way][1] and I try to follow that specification as close as possible to get a sane versioning.

It also makes filtering for those Tags easier, as you can press `v` and then the &lt;kbd&gt;TAB&lt;/kbd&gt;-key for autocompletion: This will list all the tags (and maybe a few branches), whereas there are several digits a tag could start with.

Edit: In 2019, Semver added a section to their FAQ, clarifying that the &quot;v&quot; prefix is &quot;a common way to indicate a version number&quot; (see [&quot;Is “v1.2.3” a semantic version?&quot;][2]).

----

See also: https://stackoverflow.com/questions/2006265/is-there-an-standard-naming-convention-for-git-tags


  [1]: https://github.com/semver/semver/releases/tag/v2.0.0
  [2]: https://semver.org/#is-v123-a-semantic-version

Since v stands for version, tags are generally named vX.Y.Z, with X.Y.Z following [Semantic Versioning 2.0.0][1].

This allows for branches X.Y.Z to co-exist with those tags, without having to deal with error message like &quot;fatal: Ambiguous object name&quot; (as in &quot;[Ambiguous Names with GIT?][2]&quot;).

Note that the tags for Git itself have recently been &quot;adapted&quot; for a surprising reason: see &quot;[Code version change “rules”][3]&quot;.


  [1]: http://semver.org/
  [2]: https://stackoverflow.com/questions/5307956/ambiguous-names-with-git
  [3]: https://stackoverflow.com/a/3377717/6309

https://semver.org/#is-v123-a-semantic-version

&gt; **Is “v1.2.3” a semantic version?** No, “v1.2.3” is not a semantic
&gt; version. However, prefixing a semantic version with a “v” is a common
&gt; way (in English) to indicate it is a version number. Abbreviating
&gt; “version” as “v” is often seen with version control. Example: git tag
&gt; v1.2.3 -m &quot;Release version 1.2.3&quot;, in which case “v1.2.3” is a tag
&gt; name and the semantic version is “1.2.3”.

When working with `plyr` I often found it useful to use `adply` for scalar functions that I have to apply to each and every row.

e.g.

    data(iris)
    library(plyr)
    head(
         adply(iris, 1, transform , Max.Len= max(Sepal.Length,Petal.Length))
        )
      Sepal.Length Sepal.Width Petal.Length Petal.Width Species Max.Len
    1          5.1         3.5          1.4         0.2  setosa     5.1
    2          4.9         3.0          1.4         0.2  setosa     4.9
    3          4.7         3.2          1.3         0.2  setosa     4.7
    4          4.6         3.1          1.5         0.2  setosa     4.6
    5          5.0         3.6          1.4         0.2  setosa     5.0
    6          5.4         3.9          1.7         0.4  setosa     5.4


Now I&#39;m using `dplyr` more, I&#39;m wondering if there is a tidy/natural way to do this? As this is **NOT** what I want:

    library(dplyr)
    head(
         mutate(iris, Max.Len= max(Sepal.Length,Petal.Length))
        )
      Sepal.Length Sepal.Width Petal.Length Petal.Width Species Max.Len
    1          5.1         3.5          1.4         0.2  setosa     7.9
    2          4.9         3.0          1.4         0.2  setosa     7.9
    3          4.7         3.2          1.3         0.2  setosa     7.9
    4          4.6         3.1          1.5         0.2  setosa     7.9
    5          5.0         3.6          1.4         0.2  setosa     7.9
    6          5.4         3.9          1.7         0.4  setosa     7.9

Applying a function to every row of a table using dplyr?

I am an entry-level Android software developer. I recently heard about HAXM that support emulator in rendering graphics more smoothly. I downloaded appropriate file HAXM file for Windows 7 64 bit, unpacked and started installing. However, during the installation process I get this error:

&gt; &quot;This computer meets requirements for HAXM, but VT-x is not turned
&gt; on...&quot;


I checked many forum about this problem, including checking the version of BIOS and enabling Virtual Technology on BIOS. I followed the steps posted in the following forum:

[https://stackoverflow.com/questions/16091677/intel-haxm-installation-error-this-computer-does-not-support-intel-virtualizat][2]


  [1]: http://i.stack.imgur.com/WiUqz.png
  [2]: https://stackoverflow.com/questions/16091677/intel-haxm-installation-error-this-computer-does-not-support-intel-virtualizat

However, I don&#39;t have any lines about Hyperlaunch and I could not find Hyper-V options in my Windows features. I don&#39;t have any idea how to solve this problem.

Error during installing HAXM, VT-X not working

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

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

I&#39;ve pulled all remote branches via `git fetch --all`. I can see the branch I&#39;d like to merge via `git branch -a` as remotes/origin/branchname. Problem is it is not accessible. I can&#39;t merge or checkout.

Git: Merge a Remote branch locally

The terminology used to merge a branch with an official repository is a &#39;pull request&#39;. This is confusing, as it appears that I am requesting to push my changes to the official repository.

Why is it called a pull request and not a push request?


Why is a git &#39;pull request&#39; not called a &#39;push request&#39;?

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 want to use git in Intellij Terminal but it does not recognize the command. In Command Prompt and Windows power shell the command in recognized (I added the git path in System Environment Variables). I am also aware that Intellij has an GUI integration with Git.

So, can anyone tell me how can I use the git command in the Intellij terminal.

Setup git in Intellij terminal

    MacBook-Pro:~ skbc$ pod setup --verbose
    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin13/rbconfig.rb:212: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
    
    Setting up CocoaPods master repo
    
    Cloning spec repo `master` from `https://github.com/CocoaPods/Specs.git` (branch `master`)
      $ /usr/bin/git clone &#39;https://github.com/CocoaPods/Specs.git&#39; master
      Cloning into &#39;master&#39;...

Have gone through resources provided by Cocoapods website, SO and few video tutorials. Nothing happening even after waiting for a couple of hours, however still trying to figure out what may be the problem is? 

I would very much appreciate your comments and suggestions.



Cocoapods setup stuck on pod setup command on terminal

I&#39;m still getting used to Python conventions and using Pylint to make my code more Pythonic, but I&#39;m puzzled by the fact that Pylint doesn&#39;t like single character variable names. I have a few loops like this:

    for x in x_values:
       my_list.append(x)

and when I run `pylint`, I&#39;m getting `Invalid name &quot;x&quot; for type variable (should match [a-z_][a-z0-9_]{2,30}` -- that suggests that a valid variable name must be between 3 and 31 characters long, but I&#39;ve looked through the [PEP8 naming conventions][1] and I don&#39;t see anything explicit regarding single lower case letters, and I do see a lot of examples that use them.

Is there something I&#39;m missing in PEP8 or is this a standard that is unique to Pylint?

  [1]: http://www.python.org/dev/peps/pep-0008/#naming-conventions



Why does Pylint object to single-character variable names?

I read them on [YAML-wikipedia][1] but not really understood the main difference between them. I saw there are someone using `.yaml` extension, however, **Symfony2** use `.yml` extension. 

**YAML** is a human-readable data serialization format that takes concepts from programming languages such as C, Perl, and Python, and ideas from XML and the data format of electronic mail.

**YAML** is a recursive acronym for &quot;YAML Ain&#39;t Markup Language&quot;. Early in its development, YAML was said to mean &quot;Yet Another Markup Language&quot;,[3] but it was then reinterpreted (backronyming the original acronym) to distinguish its purpose as data-oriented, rather than document markup.

So, how exactly the different between `.yaml` and `.yml`? When should we prefer one over the other?

 


  [1]: http://en.wikipedia.org/wiki/YAML

What is the difference between .yaml and .yml extension?

I&#39;m trying to determine whether there is a naming convention for the names of `const` in Golang.

I personally would tend to follow the C style and write them in upper case, but I haven&#39;t found anything on this page http://golang.org/doc/effective_go.html which seems to list some naming conventions for the language.

Go naming conventions for const

Should I give my Swift class names a three-letter prefix as recommended by [Objective-C Conventions: Class Names Must Be Unique Across an Entire App][1]?

  [1]: https://developer.apple.com/library/ios/documentation/cocoa/conceptual/ProgrammingWithObjectiveC/Conventions/Conventions.html#//apple_ref/doc/uid/TP40011210-CH10-SW4

Swift: Class Prefix Needed?

In Swift, it seems that global constants should be camelCase.

For example:

    let maximumNumberOfLoginAttempts = 10

Is that correct?

I&#39;m used to all caps, e.g., `MAXIMUM_NUMBER_OF_LOGIN_ATTEMPTS`, from C, but I want to acquiesce to Swift conventions.

Swift: Global constant naming convention?

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? 

Branching and merging best practices in Git

In my team we are migrating from svn to git and we have agreed upon embracing the git-flow flow. I&#39;ve been playing around a while with SourceTree and the Git-Flow extension. Now, we have decided that the develop branch will be called development/current instead, but I do not find in the SourceTree UI where to change the Git-Flow configuration.

Is it possible, once initialized, to change the Git-Flow configuration for a given repository?

Content Type	Original Author	Original Content on Stackoverflow
Question	friederbluemle	View Question on Stackoverflow
Solution 1 - Git	TimWolla	View Answer on Stackoverflow
Solution 2 - Git	VonC	View Answer on Stackoverflow
Solution 3 - Git	Pier	View Answer on Stackoverflow

Git flow release branches and tags - with or without "v" prefix

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

Error during installing HAXM, VT-X not working

Applying a function to every row of a table using dplyr?

Attributions