Has anyone found a meaningful way to ignore the .github directory when managing database assets with git?

The TM1Project file only enables you to ignore files within the TM1 Source directory directly.  It seems the only other file that can automatically be updated is the README.md file as noted below.

Hi Roman,

Can you elaborate a bit more on your ask? The ignore, or not ignore, section in the project file indeed only applies to objects in your project/model.

As it stands only the README.md file, if it exists, is retained, otherwise only the model content is pushed on any subsequent push. We are in the process of adding two additional capabilities, one of which would allow you to selectively push only changes made to selective objects and, secondly, allow for additional files to be included in the GIT repository used for a TM1 model/project. The latter would allow you to retain such .github directory, which I for one needed to retain my GitHub action definitions for the repository, but also other files like data pipelining definitions, editor specific setting (.vscode directory for example) etc. etc. as well.

I.o.w., reading your request above I wondered; how did you get a .github directory and where would that be (as it stands TM1's GIT integration would ignore it) and, presuming you deliberately added it to the repository to begin with, why would you want to ignore it (as it stands any push from TM1 would remove it anyway - which is what we'll prevent from happening in the future).

Has anyone found a meaningful way to ignore the .github directory when managing database assets with git?

The TM1Project file only enables you to ignore files within the TM1 Source directory directly.  It seems the only other file that can automatically be updated is the README.md file as noted below.

Hi Hubert,

We are manually adding/re-adding the .github directory post each push to maintain a CODEOWNERS file, so that we can have an approval mechanism for each PR to deploy thru our pipeline from DEV-->QA-->STAGE-->PROD.

I think the second option you mention would work for us, is there an ETA on availability on v11?  Like you mentioned that directory get's removed each time we do a push to the repository, and we need to manually perform another commit to add it back as our repository rules requires a review from CODEOWNERS prior to merging.

We're trying to think of alternatives to manually repush a global copy via our deployment scripts, but something built in would be preferred.

Hi Roman,

Can you elaborate a bit more on your ask? The ignore, or not ignore, section in the project file indeed only applies to objects in your project/model.

As it stands only the README.md file, if it exists, is retained, otherwise only the model content is pushed on any subsequent push. We are in the process of adding two additional capabilities, one of which would allow you to selectively push only changes made to selective objects and, secondly, allow for additional files to be included in the GIT repository used for a TM1 model/project. The latter would allow you to retain such .github directory, which I for one needed to retain my GitHub action definitions for the repository, but also other files like data pipelining definitions, editor specific setting (.vscode directory for example) etc. etc. as well.

I.o.w., reading your request above I wondered; how did you get a .github directory and where would that be (as it stands TM1's GIT integration would ignore it) and, presuming you deliberately added it to the repository to begin with, why would you want to ignore it (as it stands any push from TM1 would remove it anyway - which is what we'll prevent from happening in the future).

Has anyone found a meaningful way to ignore the .github directory when managing database assets with git?

The TM1Project file only enables you to ignore files within the TM1 Source directory directly.  It seems the only other file that can automatically be updated is the README.md file as noted below.