Skip to content

[packages] Move hard-coded repo/package details to config files #185364

Description

@stuartmorgan-g

As part of making the repo tools work for a second repo again, we need to move things that were hard-coded into the repo tools into config files:

  • _issueTagForPackage hard-codes label mappings
  • The repository link hard-codes a check for https://github.com/flutter/packages/tree/main as a prefix
  • The main README PR link also hard-codes that prefix
  • license_check hard-codes exceptions (We may leave this as-is; since these should be rare, and hard to add, so making it require a tool-level update is probably fine even once we are multi-repo)

(I'll update the list as I find more things.)

Metadata

Metadata

Labels

P1High-priority issues at the top of the work listp: toolingAffects the flutter_plugin_tools packagepackageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions