# Kirby Git Plugin for Kirby 3 (gcapc)

**URL:** <https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415>\
**Category:** Plugins\
**Tags:** v3\
**Created:** [January 24, 2019, 10:31am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415 "2019-01-24T10:31:16Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![mactux](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/mactux/32/12223_2.png) [@mactux](https://forum.getkirby.com/u/mactux)\
**Post date:** [January 24, 2019, 10:31am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/1 "2019-01-24T10:31:16Z")

</div>

Hey Folks, we’ve just released the first beta version of our **[git-commit-and-push-content](https://github.com/blankogmbh/kirby-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! 🙂

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [January 24, 2019, 10:36am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/2 "2019-01-24T10:36:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![bvdputte](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/bvdputte/32/8179_2.png) [@bvdputte](https://forum.getkirby.com/u/bvdputte)\
**Post date:** [January 24, 2019, 4:11pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/3 "2019-01-24T16:11:23Z")

</div>

I haven’t watched it in detail yet, but what exactly is the difference with @wottpal’s [https://github.com/wottpal/kirby-git](https://github.com/wottpal/kirby-git) plugin?

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [January 24, 2019, 5:36pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/4 "2019-01-24T17:36:39Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![bvdputte](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/bvdputte/32/8179_2.png) [@bvdputte](https://forum.getkirby.com/u/bvdputte)\
**Post date:** [January 24, 2019, 6:32pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/5 "2019-01-24T18:32:27Z")

</div>

AFAIK, [Kirby git](https://github.com/wottpal/kirby-git) also uses git for versioning. But it also has some nice additions to visualize this into the panel!

---

<div class="post-metadata">

**Author:** ![wottpal](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/wottpal/32/4439_2.png) [@wottpal](https://forum.getkirby.com/u/wottpal)\
**Post date:** [January 24, 2019, 6:53pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/6 "2019-01-24T18:53:37Z")

</div>

Hey there 👋  
Yes @bvdputte is correct mine is pushing to a „real“ git repo as well and has the panel-visualization as an additional feature 🙂  
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!

---

<div class="post-metadata">

**Author:** ![mactux](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/mactux/32/12223_2.png) [@mactux](https://forum.getkirby.com/u/mactux)\
**Post date:** [January 25, 2019, 8:08am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/7 "2019-01-25T08:08:12Z")

</div>

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”™. 😉

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.

---

<div class="post-metadata">

**Author:** ![flokosiol](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/flokosiol/32/468_2.png) [@flokosiol](https://forum.getkirby.com/u/flokosiol)\
**Post date:** [January 25, 2019, 9:00am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/8 "2019-01-25T09:00:05Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [January 25, 2019, 9:01am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/9 "2019-01-25T09:01:14Z")

</div>

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 ?

---

<div class="post-metadata">

**Author:** ![mactux](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/mactux/32/12223_2.png) [@mactux](https://forum.getkirby.com/u/mactux)\
**Post date:** [January 25, 2019, 9:13am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/10 "2019-01-25T09:13:46Z")

</div>

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. 😉

---

<div class="post-metadata">

**Author:** ![sylvainjule](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/sylvainjule/32/4338_2.png) [@sylvainjule](https://forum.getkirby.com/u/sylvainjule)\
**Post date:** [January 25, 2019, 9:53am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/11 "2019-01-25T09:53:53Z")

</div>

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 😃

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [January 30, 2019, 10:12am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/12 "2019-01-30T10:12:58Z")

</div>

Split this topic on January 30, 2019, 10:12am UTC

11 posts were split to a new topic: [Problem setting up git plugin](https://forum.getkirby.com/t/problem-setting-up-git-plugin/12564)

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [February 10, 2019, 8:53pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/13 "2019-02-10T20:53:31Z")

</div>

@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** `

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [February 12, 2019, 8:44am UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/14 "2019-02-12T08:44:15Z")

</div>

Any thoughts on this?

---

<div class="post-metadata">

**Author:** ![DanielRivers](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/danielrivers/32/176_2.png) [@DanielRivers](https://forum.getkirby.com/u/DanielRivers)\
**Post date:** [February 14, 2019, 7:14pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/15 "2019-02-14T19:14:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [February 14, 2019, 7:27pm UTC](https://forum.getkirby.com/t/kirby-git-plugin-for-kirby-3-gcapc/12415/16 "2019-02-14T19:27:46Z")

</div>

> [@DanielRivers](#):
>
> You have any ideas about this? Or should I split my repo?

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