|
| 1 | +name: Adopter — we're using coder_eval |
| 2 | +description: Tell us your team uses coder_eval so we can add you to ADOPTERS.md |
| 3 | +title: "[adopter] <organization>" |
| 4 | +labels: ["adopter"] |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + Thanks for using coder_eval! Adopter entries help other teams see the project is |
| 10 | + real and in production, and they tell us which use cases to keep supporting. |
| 11 | +
|
| 12 | + Everything below is optional except the organization and how you use it. We only |
| 13 | + publish what you explicitly allow here. |
| 14 | + - type: input |
| 15 | + id: organization |
| 16 | + attributes: |
| 17 | + label: Organization |
| 18 | + description: The name you'd like listed. |
| 19 | + placeholder: Acme Corp |
| 20 | + validations: |
| 21 | + required: true |
| 22 | + - type: input |
| 23 | + id: website |
| 24 | + attributes: |
| 25 | + label: Website |
| 26 | + placeholder: https://example.com |
| 27 | + validations: |
| 28 | + required: false |
| 29 | + - type: textarea |
| 30 | + id: usage |
| 31 | + attributes: |
| 32 | + label: How do you use coder_eval? |
| 33 | + description: | |
| 34 | + A sentence or two. What do you evaluate — Claude Code skills, agent A/B tests, |
| 35 | + CI quality gates, your own repos — and roughly at what scale? |
| 36 | + placeholder: | |
| 37 | + We gate CI on a suite of ~40 YAML tasks that check our internal Claude Code |
| 38 | + skills still trigger, and A/B Claude Code against Codex each release. |
| 39 | + validations: |
| 40 | + required: true |
| 41 | + - type: dropdown |
| 42 | + id: listing |
| 43 | + attributes: |
| 44 | + label: How may we list you? |
| 45 | + description: | |
| 46 | + Pick the most you're comfortable with. **Logo use needs someone who can approve |
| 47 | + trademark use for your organization** — if that isn't you, choose a name-only or |
| 48 | + private option and we'll follow up. |
| 49 | + options: |
| 50 | + - Name only, in ADOPTERS.md |
| 51 | + - Name in ADOPTERS.md and on the project website |
| 52 | + - Name and logo in ADOPTERS.md and on the project website |
| 53 | + - Please don't list us publicly — this is just for the maintainers |
| 54 | + default: 0 |
| 55 | + validations: |
| 56 | + required: true |
| 57 | + - type: checkboxes |
| 58 | + id: logo-permission |
| 59 | + attributes: |
| 60 | + label: Trademark permission |
| 61 | + description: Only required if you selected a logo option above. |
| 62 | + options: |
| 63 | + - label: >- |
| 64 | + I am authorized to grant this permission on behalf of my organization, and I |
| 65 | + grant the coder_eval maintainers a non-exclusive, revocable license to display |
| 66 | + our name and logo as an adopter in ADOPTERS.md and on the project website. We |
| 67 | + can withdraw it at any time by commenting on this issue. |
| 68 | + required: false |
| 69 | + - type: input |
| 70 | + id: contact |
| 71 | + attributes: |
| 72 | + label: Contact |
| 73 | + description: GitHub handle or email, so we can reach you before publishing anything. |
| 74 | + validations: |
| 75 | + required: false |
| 76 | + - type: checkboxes |
| 77 | + id: case-study |
| 78 | + attributes: |
| 79 | + label: Anything else? |
| 80 | + options: |
| 81 | + - label: We'd be open to a short case study or a talk about our setup. |
| 82 | + required: false |
| 83 | + - label: We'd like to hear about breaking changes before they ship. |
| 84 | + required: false |
0 commit comments