How about sending us a pull request which merges all .gitignore files
into one in the toplevel directory, Steve? :D We'd be glad to apply it.
Regards, mg
Am 25.02.13 20:08, schrieb Steven Carr:
> On 25 February 2013 18:37, Michiel Beijen wrote:
>> There are a multitude of .gitignores all over th
On 25 February 2013 18:37, Michiel Beijen wrote:
> There are a multitude of .gitignores all over the place
That is very messy, maybe some housekeeping is in order?
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: ht
There are a multitude of .gitignores all over the place
https://github.com/OTRS/otrs/blob/master/Kernel/.gitignore
for instance ignores Kernel/Config.pm
You can run OTRS from Git and have it ignore var/article, log files, etc.
This is also how it would work on developer systems, we want to ignor
Nope, still not in the tree. If you look at
https://github.com/OTRS/otrs/blob/master/.gitignore there is nothing
in there ignoring Config.pm, GenericAgent.pm, Ticketcounter.log, /var
data directories etc. etc.
The support module has been ignored but it would be good if other
modules could be ignor
Hi Steve,
that should be the case now, can you try?
We already received 5 pull requests, amazing!
Regards, mg
Am 22.02.13 15:42, schrieb Steven Carr:
> Fantastic!
>
> Would it be possible to have the .gitignore updated to exclude all
> locations that OTRS "writes" to (or what settings are required
> Would it be possible to have the .gitignore updated to exclude all locations
> that OTRS "writes" to (or what settings are required so can I configure OTRS
> to store it's data/configuration in a completely separate location). So that I
> can keep my local OTRS installation up-to-date with git bu
Fantastic!
Would it be possible to have the .gitignore updated to exclude all
locations that OTRS "writes" to (or what settings are required so can
I configure OTRS to store it's data/configuration in a completely
separate location). So that I can keep my local OTRS installation
up-to-date with gi
Dear all,
as some of you may have already noticed, the OTRS framework,
documentation and some utility modules have been migrated to git. We
have updated the usage instructions on the website and in the
documentation. If you still find places with outdated information,
please let us know. We also p