-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH Update reference to supported modules data #136
ENH Update reference to supported modules data #136
Conversation
@GuySartorelli is attempting to deploy a commit to the SilverStripe Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
"silverstripe/silverstripe-userhelp-content", | ||
"silverstripe/demo.silverstripe.org", | ||
"silverstripe/silverstripe-frameworktest", | ||
"silverstripe/developer-docs", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this list by dynamically read from the supported-modules repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not on every request, no. This file gets rebuilt based on the supported-modules
repo data on each deployment, as per the information in the readme. This is the way it has always worked.
We just need to make sure to trigger a deployment if we update the list, which was already required before this PR anyway. I'm not inclined to change the way that works in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No longer hardcoding repos - the supported-modules list has all the repos we care about.
Added "other" category, so maintenance repos aren't dumped into the "supported" list.
Issue