-
Notifications
You must be signed in to change notification settings - Fork 42
docs: rename platforms to clientPlatforms and update examples #225
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: Copilot <[email protected]>
|
Why is this garbage Copilot bot commenting on PRs? |
|
|
@rantoniuk thanks for the PR! FYI, changing the name would be a breaking change, and breaking changes need to go through a process of deprecating the thing first: see https://github.com/publiccodeyml/publiccode.yml/blob/main/governance/procedure-proposing-changes-and-voting.md Anyway, I don't think changing the name would be necessary, as we can make clear what that key is about by improving its description. The description, on the other hand, badly needs to be improved because right now it is pretty cloudy, and I think it's because the meaning of the key itself is pretty cloudy :) I'd like to discuss and have a consensus on what this key is supposed to achieve on #221 before |
Didn't we already discuss and agree? |
I haven't really shared my thoughts yet. I have something else in mind, let me write that down in the issue. |
#221