Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update gitignore with additional Copado elements #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update gitignore with additional Copado elements #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,23 @@ installedPackages/*
#It is recommended that you ignore managed components that cannot be modified
#since there is no need to track them in Git, like for example:

applications/copado__*
classes/copado__*
customPermissions/copado__*
dashboards/copado__*
email/copado__*
triggers/copado__*
pages/copado__*
workflows/copado__*
objects/copado__*
objectTranslations/copado__*
layouts/copado__*
Copy link

@drcopa drcopa Nov 15, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some customers personalize Copado in Sandboxes and then deploy the changes using Copado. I originally included some of these lines in the gitignore but customers opened cases because Copado changes in objects/layouts did not appear when committing them to Git. To avoid these type of cases we only included metadata types in the gitignore that cannot be modified in Managed Packages (apex classes, etc).
I would do the same in your changes, only leave the ones that cannot be modified.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds fair.
Maybe include the rest commented with a note

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that would be good!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about something like:

classes/*__*
triggers/*__*
pages/*__*
components/*__*

reports/copado__*
reportTypes/copado__*
sharingRules/copado__*
staticresources/copado__*
permissionsets/copado__*
tabs/copado__*

#profiles and permission sets are complex Files. If your Org's metadata and Git are in sync,
#you can track incremental changes on Profiles and Permission sets using Copado "commit files" functionality.
Expand Down