.proj file suggestion

[lordnynex]

Regarding my 'best practices' issue. I think a cool enhancement would be to manage .proj file in a separate branch entirely. Something like:

• pull 'asana-hub-proj' from origin
• create a local branch named 'asana-hub-proj-(date +%s)'
• write proj file changes
• merge to 'asana-hub-proj'
• push 'asana-hub-proj' to origin
• delete local branch

Benefits:

• proj files stay out of key branches
• multi-developer don't need to worry about keeping this file in sync across develop/feature branches
• no rebasing/merge conflict weirdness
• merge masters know to never merge this special branch
• can easily make a cron job on some system to perform periodic sync's

[lordnynex]

Additional benefit is the addition of branch exceptions to ci files.

branches:
  except:
    - asana-hub-proj