adopted-ember-addons / adopted-ember-addons/program-guidelines

Improve consistency of addons in this org for maintenance

未關閉
#28 25 則留言 9 個 reaction 已指派 1 人 已被 @MelSumner 認領 在 GitHub 檢視
proposal
主要語言
JavaScript
星號
4
分支
4
PR 合併指標
30 天內沒有已合併 PR

描述

There are a lot of times when I struggle to update or release one of these addons (in the org) because they're all using different configurations.

I'd like to propose that we adopt these standards:

- The primary branch of all repos is `main`
- All packages use `pnpm`
- All packages use `release-plan` (setup instructions here: https://github.com/mansona/create-release-plan-setup)
- ensure each repo has a consistent github ci workflow file
- ensure each repo is using `ember-try`
- use dependabot, use consistent config

For settings:

- update settings so a PR is required
- branches should be deleted after merge
- we'll add a consistent social preview image to each repo

If an addon should be archived:

- file an issue on that repo and let us know in the Discord channel

Did I forget anything?

cc @adopted-ember-addons/admin
```[tasklist]
### Tasks
- [ ] Create template maintanance project
- [ ] Update documentation for this org
- [ ] Add project to each repo in org
```

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。