Kirby Git Plugin for Kirby 3 (gcapc)

Plugins Kirby 3 plugin šŸ§©
1

Hey Folks, weā€™ve just released the first beta version of our git-commit-and-push-content plugin for Kirby 3.

Since plugins for Kirby 3 work differently the new version will not be compatible with Kirby 2. But you can still use version 2 of the plugin.

To install via composer add "blankogmbh/kirby-git-commit-and-push-content": "^3.0.0-beta.1" to your require section. You also need to add "minimum-stability": "dev" to your composer.json to allow unstable versions.

Pullrequests, GitHub issues, and feedback are very welcome! :slight_smile:

5 Likes
2

My Hero! I will be giving this a go over the next couple of days

1 Like
3

I havenā€™t watched it in detail yet, but what exactly is the difference with @wottpalā€™s https://github.com/wottpal/kirby-git plugin?

4

This one (correct me if I am wrong) pushes to a real git repo, the other one I think its kirby internal version control (at least that what it looks like)

5

AFAIK, Kirby git also uses git for versioning. But it also has some nice additions to visualize this into the panel!

6

Hey there :wave:
Yes @bvdputte is correct mine is pushing to a ā€žrealā€œ git repo as well and has the panel-visualization as an additional feature :slight_smile:
Havenā€™t tested it with the stable version yet though. But with the RCs it worked fine.

If you want to collaborate feel free to send PRs and I can also give you/your team special repo access-rights!

3 Likes
7

Hi! Weā€™ve not noticed @wottpal forked our plugin, so we started porting ours to Kirby 3. But your changes look very good, so I think itā€™s a good idea to start collaborating on this, so we can build ā€œThe best Kirby git experience everā€ā„¢. :wink:

I have a lot of stuff on my list for today but Iā€™ll come back to you when I have a bit more time.

7 Likes
8

Awesome. Great news to hear that there will be one unified amazing Git Plugin!

9

Will be great if you guys can work together on this, I think its a great idea. Question I have now though is, which should I use today? @mactux or @wottpal ?

10

If you want to have the history view in the Panel you might want to go with @wottpalā€™s. If you want/need to install the plugin via composer you probably should use ours. :wink:

1 Like
11

Thanks to both of you for creating these!

I would love to be able to skip the automated part on some projects, and have a ā€œCommit changesā€ button I can put somewhere, where I enter a more explicit commit name, like ā€œAdded 3 projectsā€ or ā€œUpdated my info with publicationsā€, and it pushes all the changes since the last commit.

Would allow for more explicit commit messages and less commits overall, so a more readable repo. Iā€™d gladly open a ticket on github somewhere, or try and PR something for this, but Iā€™ll wait for an unified repo then :smiley:

2 Likes
12

11 posts were split to a new topic: Problem setting up git plugin

13

@mactux I am finally installing this one my site, I have installed, looking ā€˜okā€™ so far.

This is my config, reason for the Kirby()->root() is because I have a repo at that the root level and rather not have 2 separate repos, one for the site and one for the content.

   'blankogmbh' => [
        'gcapc' => [
            'commit' => true,
            'push' => true,
            'path' => kirby()->root()            
        ],
    ],

But with that config, my site gives me **Fatal error** : Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in **C:\xampprb\htdocs\kirby\config\roots.php** on line **6**

14

Any thoughts on this?

15

@mactux You have any ideas about this? Or should I split my repo?

16

@DanielRivers Maybe add an issue in their repo, donā€™t count on people following forum threads here closely.