I think most people just keep test cases in the repo and push them out with
production. Secondary files like design docs can be kept in a branch if you
don't want them in the main branch. You can even pull them out into their
own repo if you want, that may be simpler to manage.
Tekkub
GitHub Tech Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Thu, Jan 21, 2010 at 9:24 PM, Michael Filbin <[email protected]>wrote:
> Here is my problem.
>
> I have a project that uses a git-centric workflow (courtesy of
> Heroku). Typically, I commit changes to my repository which then
> triggers a hook to push the newly committed source to Heroku (my
> production server). I have RSpec specification files, cucumber user
> stories, and other types of supplemental files that really have no
> business or value being on the production server, but really need to
> be under version control. I would like to have my local repository
> acting as the "central" repository containing a version history of all
> files. I would then like push the entire project source to a GitHub
> repository and then selective files to the Heroku production server.
>
> I would like to use a "best practice" is such a thing exists for this
> type of situation, but it seems to me that its a reasonable enough
> situation that perhaps many of you have experienced this before. The
> need for a best practice solution is because I may have more
> collaborators on this project in the future and eventually I would
> like to pass it along. It's an investment.
>
> Is something like this typically accomplished through branching, which
> doesn't feel appropriate to me? Can you have two repositories within
> the same top-level directory of a project? I doubt they could coexist
> let allow the lack of efficiency by constantly repeating the same
> actions.
>
> What would you do in my situation? Thanks for your help.
>
> - Mike
>
> --
> You received this message because you are subscribed to the Google Groups
> "GitHub" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<github%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/github?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/github?hl=en.
