You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.
Just a few questions on best practices using SCM. Should the .proj file be stored in scm? If so, how do you deal with feature branches and teams? Would be cool if there was a small blurb in the docs about this.
The text was updated successfully, but these errors were encountered:
To be honest, after having used asana-hub internally for a few months now, we're really feeling the lack of the "instant gratification factor"
We may be moving it to a daemon tool, but nevertheless, you're absolutely right about adding documentation for best practices!
To quickly address - we keep our .proj in our github repository on the master branch. I have the repo checked out separately to manage this, and I occasionally run sync (maybe every hour or so) which updates the .proj in place. Then I commit these changes to the repo, rinse, and repeat. (I commit at the end of the day only once per day)
Because the commits are only to this file, there is no fear of conflicts unless I'm syncing from two places at once, which is not a great idea.
soundofjw
changed the title
best practices
best practices documentation
Sep 17, 2015
Hello,
Just a few questions on best practices using SCM. Should the .proj file be stored in scm? If so, how do you deal with feature branches and teams? Would be cool if there was a small blurb in the docs about this.
The text was updated successfully, but these errors were encountered: