Child pages
  • Add .gitignore files to In-Portal [5.3.0-B1]
Skip to end of metadata
Go to start of metadata

Right now with svn:ignore properties under SVN all works as a charm, but it becomes problematic to figure out what exactly is ignored if there is a need.

Consider following workflow:

  1. developer downloads a ZIP with official release content
  2. imports it into his repository (SVN or GIT)
  3. performs installation
  4. makes changed to a code
  5. tries to commit

At commit time all stuff, that In-Portal have created during runtime in /system/ folder is displayed as changes that needs to be commited. This is very problematic for a newcomer to determine what really needs to be commited and what not.

To solve this I'm proposing to add .gitignore files where .cvsignore files used to be. This not only eases In-Portal transition to GIT (if that happens), but also allows to reset svn:ignore properties with a single bash command by scanning created .gitignore files.

Here are current values:

Foldersvn:ignore
.

testing
.buildpath
.idea
.project
.settings

core/admin_templates/themes.dev
system/user_files

*
*.*

system/tmp*
*.*
system*
*.*
system/cache*
*.*
core/admin_templates/js/jqueryjquery.unpacked.js
system/images/emoticons*
*.*
system/images*
*.*
core/unitsconfig_editor
core/admin_templatesconfig_editor
system/user_files/icons*
*.*
toolsinternal
core/admin_templates/jsscript_n.js
system/.restricted*
*.*
system/images/pending*
*.*

All of above properties were retrieved using following command executed on "in-portal" module checkout directory:

svn pg svn:ignore --recursive

As you can see from a table there 3 folder types where this property is set:

  1. /system folder and it's sub-folders
  2. some strange folder
  3. tools/home folder

I've highlighted properties, that are no longer needed (in my opinion) in bold.

Related Tasks

INP-1290 - Getting issue details... STATUS

1 Comment

  1. Let's create a task for this in 5.3.0 - minor, but should resolved.