Issues · Extensions / extensions-directory · GitLab

Proposal: review approval indicated with tag or "@somebody please release", etc.

#53 · opened Aug 04, 2020 by AllenShaw
- 2
updated Aug 05, 2020
Update "labels" wiki page to clarify it's talking about "topics" not labels

#52 · opened Jul 06, 2020 by DaveD
- 0
updated Jul 06, 2020
CiviDesk says they're no longer maintaining com.cividesk.email.sparkpost - should it be marked deprecrated?

#49 · opened Jun 30, 2020 by herbdool
- 3
updated Jul 02, 2020
Should Civi core provide a secure, standardized approach if extensions want to provide automatic self-updating? (Such as what CiviMobileAPI does)

#48 · opened Jun 18, 2020 by herbdool
- 5
updated Jun 18, 2020
Automatically create a repo on lab.c.o when a new extension is added on c.o

#47 · opened May 30, 2020 by bgm
- 1
- 6
updated Jul 01, 2020
Automatic releases and extension third-party libraries

#45 · opened May 18, 2020 by bgm
- 5
updated Jun 01, 2020
Proposal: Simpler review process for trusted developers (for automatic in-app distribution)

#44 · opened Apr 28, 2020 by bgm discussion
- 1
- 17
updated Aug 06, 2020
Make searching GitLab (Extensions) easier with an external search integration...

#42 · opened Oct 08, 2019 by MikeyMJCO
- 2
- 0
updated Oct 08, 2019
Add hook to check info.xml version number on pushing tags

#40 · opened Oct 08, 2019 by sluc23
- 1
updated Oct 11, 2019
GitLab CI for basic extension review checks.

#39 · opened Oct 08, 2019 by MikeyMJCO
- 0
updated Oct 08, 2019
Extensions directory v2019.10

#38 · opened Jul 19, 2019 by totten
- 15
updated Jul 24, 2019
Meta-Level Question: GSOC Projects - include them on GitLab or GitHub/make them more accessible?

#29 · opened May 15, 2019 by CM Toolan
- 1
- 1
updated May 22, 2019
"The Fully Qualified Name did not match parent extension" validation failure

#21 · opened Nov 20, 2017 by xurizaemon
- 1
updated Nov 20, 2017
Automated release system email warning about older release

#20 · opened Nov 19, 2017 by xurizaemon
- 2
updated Nov 20, 2017
Condense Installation x 3 to a single header with more explanation

#19 · opened Nov 06, 2017 by Michael McAndrew
- 1
- 2
updated Nov 08, 2017
word change to heading USAGE

#18 · opened Nov 06, 2017 by AnneDru
- 1
- 3
updated Nov 07, 2017
Add link to further documentation

#17 · opened Nov 06, 2017 by Michael McAndrew
- 1
- 1
updated Nov 07, 2017
Prepare specification of information that will assist users in deciding whether to install an extension

#16 · opened Nov 02, 2017 by ginkgofjg
- 1
updated Nov 16, 2017
Expose "available for automated download" field to anonymous users on c.o

#15 · opened Nov 02, 2017 by AllenShaw
- 0
updated Nov 02, 2017
boilerplate for extension readme and documentation

#13 · opened Oct 11, 2017 by Michael McAndrew
- 1
- 8
updated Nov 06, 2017