Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 10 14:38
    elgalu opened #597
  • May 14 09:55
    Dmitry-Erokhin opened #595
  • Apr 13 18:31
    JuroOravec opened #593
  • Apr 13 18:19
    JuroOravec opened #592
  • Apr 13 17:40
    JuroOravec opened #591
  • Oct 31 2019 14:50
    GeorgySerga opened #587
  • Jul 17 2019 10:23
    itsthejb edited #582
  • Jul 17 2019 08:36
    itsthejb opened #582
  • Jun 12 2019 09:33
    startnow65 closed #561
  • May 29 2019 15:02
    rashamalek labeled #579
  • May 29 2019 15:02
    rashamalek opened #579
  • May 13 2019 20:50
    luhaixun closed #578
  • May 11 2019 23:29
    luhaixun opened #578
  • May 10 2019 06:04
    scherniavsky assigned #575
  • May 10 2019 06:04
    scherniavsky closed #575
  • May 09 2019 14:33
    scherniavsky opened #575
  • Apr 05 2019 10:19
    itachi3 opened #572
  • Feb 11 2019 10:56
    startnow65 edited #565
  • Feb 11 2019 10:55
    startnow65 opened #565
  • Jan 24 2019 09:57
    drummerwolli edited #562
Nikolaus Piccolotto
@prayerslayer
test
Jérémy Benoist
@j0k3r
hello guys, just reached the room from twitter
I was wondering if zappr can work for private repo too? I just tried your saas version and it request only the public repo. I quickly reached the help on readthedoc to see if a parameter can be set on the backend part but didn't find it.
Nikolaus Piccolotto
@prayerslayer
Hi, currently only public repositories are supported as we ask for public_repo scope. However we would find it cool to give our users the choice between various levels of access.
There is an issue already, but not much else zalando/zappr#90
Jérémy Benoist
@j0k3r
okay
Nikolaus Piccolotto
@prayerslayer
Sorry to disappoint
Jérémy Benoist
@j0k3r
no problem, the project is still young, I was just wondering if it was possible :)
Asko Kauppi
@akauppi
I just love Gitter, so hopefully this gets back to life.
Q: Zalando documentation here (internal link) says that for docs and tools, 4 eyes principle is not required.
However, it is not enough to have in .zappr.yaml: X-Zalando-Type: doc. One also needs approvals: minimum: 1. Is this intentional - to me it would feel that the default for doc and tools should be approvals.minimum 1.
Kuba
@jglapa
Hi, anybody here?:)
Jonathan Crooke
@itsthejb
Hi everyone. Trying to improve our approval patterns here, but it's not working. Can anyone advise?
pattern: ":\\+1:|:pray:|:shipit:|👍|🙏|✅"
Would like to have the approval anywhere in the message, and added a few options, but none are accepted :(
Vlad Tsepelev
@yetithefoot
Hello, is anybody here?

I'm trying to apply PR merge veto by labels

pull-request:
  labels:
    required:
      - Release

But anyway getting zappr/pr/labels — No required labels are configured. status by Zappr. Any advice?