Do not extract category names into elements any more, instead keep the ids. In order to not introduce a BC suddenly to existing installations, adds a config option category_ids_in_elements which needs to be set to true in .gitify file to activate ids in favor of names.
Why is it needed ?
There are problems when categories have the same names.
Related issue(s)/PR(s)
I see that just as an intermediate solution - i prefer having https://github.com/modmore/Gitify/issues/165 being implemented, as this would give much more file "overview" in larger projects and reflect the tree like structure in the manager better (same as with resources/content, which is already extracted into folders)
What does it do ?
Do not extract category names into elements any more, instead keep the ids. In order to not introduce a BC suddenly to existing installations, adds a config option
category_ids_in_elements
which needs to be set to true in .gitify file to activate ids in favor of names.Why is it needed ?
There are problems when categories have the same names.
Related issue(s)/PR(s)
I see that just as an intermediate solution - i prefer having https://github.com/modmore/Gitify/issues/165 being implemented, as this would give much more file "overview" in larger projects and reflect the tree like structure in the manager better (same as with resources/content, which is already extracted into folders)