Making WordPress.org

Opened 20 months ago

Closed 20 months ago

Last modified 20 months ago

#6492 closed enhancement (fixed)

Add org SVN secrets to two-factor repo

Reported by: jeffpaul's profile JeffPaul Owned by: dd32's profile dd32
Milestone: Priority: normal
Component: Version Control Keywords:
Cc:

Description

We are looking to automate the plugin deploys for the Two-Factor plugin from GitHub to SVN like was done for the Rollback Update Failure plugin in #5803. According to https://meta.trac.wordpress.org/ticket/5803#comment:5 I'm hoping it will be as simple as adding the /two-factor/ repo to access the SVN_USERNAME and SVN_PASSWORD secrets at https://github.com/organizations/WordPress/settings/secrets/actions.

Change History (3)

#1 @dd32
20 months ago

  • Owner set to dd32
  • Status changed from new to reviewing

#2 @dd32
20 months ago

  • Resolution set to fixed
  • Status changed from reviewing to closed

@JeffPaul I've flipped the switches on, and as you'll see from emails, added the committer to the plugin too.

Please note: As a result of this, the plugin has been opt'd in to release confirmations, that means you'll have to click confirm on WordPress.org/plugins before the plugin release actually goes out, all committers will get the email and only one needs to click it.

Release Confirmation is kind of the 2-factor replacement for WordPress.org currently, because there's no easy way to do SVN 2FA that we really want to support.

#3 @JeffPaul
20 months ago

Release Confirmation is a happily accepted extra step to allow the GitHub-to-SVN deploy and ensuring releases only happen by purposeful human interaction. Thanks for getting this set up!

Note: See TracTickets for help on using tickets.