Github user swill commented on the issue:
https://github.com/apache/cloudstack-www/pull/34
So how would this work? We would have a `.gitignore` tracked in `master`
which would make the `content` folder untracked? The `.gitignore` tracked in
the `asf-site` branch would not include the `content` directory?
So then when you develop, it would not be as simple as a `merge` from
`master` into `asf-site` anymore because the tracked files are not consistent
between those branches anymore.
Would the flow be something like this then:
- Get the PR approved in `master`.
- Do a `merge` from `master` to `asf-site`.
- Run the `./build.sh` script in `asf-site`.
- Push code to `asf-site` branch.
Does that seem right? We would have to do a `git rm` of the content on the
`master` branch and then update the `.gitignore` tracked in that branch.
I don't think we need to worry about these changes in this PR though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
