Resolving the `this-property-fallback` deprecation

[david (David Taylor)]

@pfaffman

It would be nice if there were some automated way to copy/remove the proper files in each plugin when there was an update to the skeleton. (I may or may not have contrived to do that by hand this time.) Maybe it’d be possible to stick a little bash script into the skeleton that would check for plugin.rb in the current directory, and if it was there, it could copy stuff from where the script was into the current directory. Something like that.

We haven’t really publicised it, but you might be interested in GitHub - discourse/mass-pr: A tool for applying automated changes across a large number of GitHub repositories · GitHub. We use it to apply these kinds of changes across the 600+ theme/plugin repos we maintain.

So in this case, I run something like:

GITHUB_TOKEN=... pnpm mass-pr \           
  --message "DEV: Update linting" \
  --branch "update-linting" \
  --script scripts/update-js-linting.sh \
  discourse-solved \
  discourse-assign \
  ...

and it updates the skeleton stuff, autofixes all linting, and creates the PR on GitHub.

Then we have another script to handle the merging: GitHub - discourse/mass-merge: A script for mass-approving and merging Dependabot pull requests · GitHub

Definitely pr-welcome on a lighter-weight update script though! These ones are a bit heavy-handed if you only have one repo to update.