Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

best practices documentation #68

Open
lordnynex opened this issue Sep 17, 2015 · 2 comments
Open

best practices documentation #68

lordnynex opened this issue Sep 17, 2015 · 2 comments
Assignees

Comments

@lordnynex
Copy link

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.

@soundofjw
Copy link

Hi @lordnynex ! Thanks for using asana-hub 💃

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 soundofjw changed the title best practices best practices documentation Sep 17, 2015
@soundofjw soundofjw added this to the v0.3 - Advanced Sync milestone Sep 17, 2015
@soundofjw soundofjw self-assigned this Sep 17, 2015
@lordnynex
Copy link
Author

Thanks for the reply. I'll stick a bash wrapper for this in cron. Can't wait for v0.3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants