Right now regardless whether a project is published on GH or BB we produce the same files. Some files are important when opensourcing a project whereas for internal usage only some are superfluous.
The idea is that when selecting BitBucket Server as VCS we can assume that the project won't be opensourced. In that case we should clean up all files related to OSS in the post hook.
If someone decides to opensource the projects the template can be again applied with GH as VCS and the important files will be generated again.
Description
Right now regardless whether a project is published on GH or BB we produce the same files. Some files are important when opensourcing a project whereas for internal usage only some are superfluous.
The idea is that when selecting BitBucket Server as VCS we can assume that the project won't be opensourced. In that case we should clean up all files related to OSS in the post hook.
If someone decides to opensource the projects the template can be again applied with GH as VCS and the important files will be generated again.