[wp-meta] [Making WordPress.org] #6087: Provide a GitHub Integration for Plugins

[Making WordPress.org]

#6087: Provide a GitHub Integration for Plugins
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  feature request   |      Status:  new
 Priority:  low               |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by seebeen):

 A lot of time has passed since my last comment here, and I've learned a
 lot in the meantime.

 Before I dive in - keep in mind that I speak as:
  - A WordPress developer who regularly publishes to both wp.org and our
 own private WP repo.
  - A PHP developer who developed a composer module for easy updates from
 private repositories ([https://github.com/oblakstudio/wp-package-updater
 link])
  - A [https://github.com/semantic-release/wordpress semantic-
 release/wordpress] maintainer.

 > As someone who doesn't release composer modules, would my assumption
 that it simply polls Github for new Releases and pulls the Release /
 Revision / etc from there be correct?
 >@dd32

 Yes, but packagist / composer is an entirely different ballgame than WP
 plugins. Composer packages are published as is. And you download them
 straight from github tag. No build process, etc. Everything happens on the
 developer's or a CI machine. That's why vendor directory is not pushed to
 github, but is in a release tarball / zip.

 Github secrets are a reliable way of keeping, well, secrets - and they are
 secure. There is leakage potential, but GitHub does a pretty good job of
 detecting and notifying you about those possibilities. So an individual
 needs to be really stubborn and ignore all warnings in order to leak them.

 Having a native option would be very hard and very resource intensive for
 everyone on wp.org side, because most of the plugins need to fetch
 composer packages, run tests, build assets. It's all done on CI.

 Only possibility I can see so far, is to get the release zip files
 directly from github releases and then unzip them directly to SVN.

 If you think that route is doable - we can work together so I can develop
 the semantic-release plugin with that in mind - because it already builds
 a zip file with attached readme and assets.

 On my end, I'm gonna implement the entire push to SVN from the plugin in
 the coming months so devs who work on github can have a unified solutioin
 for release / deployment to .org (and private repos).

 Looking forward on hearing your input 😊

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6087#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org