-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should I pull the develop branch before starting a new feature ? #75
Comments
Definitely! You should always start with the most current develop branch to
mitigate merging issues...
…On Mon, Jan 23, 2017 at 3:28 PM, Mohammad Fares ***@***.***> wrote:
Should I pull the develop branch before starting a new feature ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#75>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA4mnRledhVvVhHaaCaRu6LXvwhCuYxSks5rVLkagaJpZM4LrGl7>
.
|
I don't see any development branch. If I translate it to Hungarian based on a fork of the gh-pages branch, will the PR dry out like the Azerbajani translation PR? |
Sorry, it's not the develop branch but directly the gh-pages branch. And no, it won't dry out - I'm having time on my hands again to support the PRs |
I did a |
Should I pull the develop branch before starting a new feature ?
The text was updated successfully, but these errors were encountered: