Exclude files or subfolders from beeing published

Feedback Studio
,
1

Hello,
I think it would be a good idea if it would be possible to exclude files or subfolders from beein published. I ask for this feature because while developing I have folders containing files which are only needed while developing. I do not want to delete them before publishing as they would probably be needed if I have to do bugfixing or implement additional requirements.

Kind regards
Martin

2

Hi @martinN,
Thank you for your suggestion.

3

This is a very well thought out feature. Thanks for the suggestion

4

Hi @Pablito, Could you prioritize this issue as the .git folder when used could go up in megabytes and hinder the deployment process.

3 Likes
5

Does anyone know if this has been implemented?

My git folder is preventing me from Pushing to Orchestrator and its annoying

6

Hello All,

A work around I found was to go into the properties of the git folder, and set it as hidden and then push to orchestrator. This seems to exclude the git folder and its subfolders from the package.

Yusuf

7

Yes, I think it is implemented partially. You can right click on a file and select “Ignore from publish”. I don’t know why that is not also possible for folders. But in my opinion that will already help a lot.

8

Hi @martinN,

Yes, the same way as it is available for test cases and xaml files with the option “Ignore from Publish”.

Thanks for bringing this up.

Regards
Sonali

9

is there any update regarding this idea?

10

I’ve had a look right now on the latest Community 2023.8, and I can see that an option to Ignore from Publish has appeared :slight_smile:
image

2 Likes
11

thank you for your update.

13

Unfortunately, Ignore from Publish isn’t an option when publishing an Object Respository.
Studio 2023.10.4 (Enterprise)
I had hoped that marking a file Make Private and changing the Include Sources setting to ‘No’ would prevent it from being packaged, but this didn’t work either. Maybe that’s only for private .xaml files?

image
image366×506 11.9 KB

Manually editing the project.json works in this case, though.
Not optimal but better than nothing.