Shared coding standards across projects #34
theguild-bot
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
General guidelines and goals
Instructions, shared config and actual pipelines code is here: https://github.com/the-guild-org/shared-config/
Changesets
Things we want from
changesets
:Be on the adopters listPR:https://github.com/changesets/changesets/pull/792I~~~~mprove reliability and reduce issues with NPM publish command, and have better support for projects with many packages.https://github.com/dotansimha/graphql-yoga/blob/master/patches/%40changesets%2Bcli%2B2.22.0.patch#L10Big repos tends to run a lot of npm commands, and the default limit is 40, which leads to a lot of rate-limit errors.PR to fix that:https://github.com/changesets/changesets/pull/853peerDependencies
are being upgraded.Easy support for alpha/canary releases based on Git (today we do this with patches)PR:https://github.com/changesets/changesets/issues/855https://github.com/dotansimha/graphql-yoga/blob/master/patches/%40changesets%2Bassemble-release-plan%2B5.1.2.patchSupport for automatic changesets for Renovate PRs (so dependencies upgrade will also be documented well in CHANGELOGs)Make GitHub release page aggregate multiple releases to make it more readablePR to add support for this feature:https://github.com/changesets/action/pull/193Related:https://github.com/changesets/changesets/issues/320Related:https://github.com/changesets/changesets/issues/683Might be related:https://github.com/changesets/changesets/issues/655https://tortilla-hq.slack.com/archives/CAYJ1G1DY/p1654581149381409@dotansimha: this is actually not the issue, we need to modify the changesets GH Action code, to support a mode where we publish a single GH Release per Changesets PR.https://github.com/the-guild-org/external-board-tasks/issues/92GitHub Actions
Often a PR is blocked by prettier (e.g. if it is a documentation only update). In that case we need to ping the PR creator or checkout the PR manually. Instead we could have a bot that runs prettier and creates PR suggestions. This could be done either automatically or via a command
@the-guild-bot format
(https://tortilla-hq.slack.com/archives/C03B470CJCT/p1660649548686799)Typescript
Memory leaks
Repositories
Beta Was this translation helpful? Give feedback.
All reactions