Guidance for submissions involving paid services

[aaronpowell]

We're open to contributions related to paid or commercial tools. But this repo is not a marketing channel.

If a submission is mainly promoting a product, driving signups, or pushing a service rather than helping people use GitHub Copilot, it's probably not a good fit.

What we welcome

We welcome contributions that are:

• technically useful
• broadly relevant to the community
• neutral in tone
• clear about setup, requirements, and limitations

That can include paid or vendor-backed services, as long as the content is primarily practical guidance.

What we may decline

We're less likely to accept submissions that:

• read like a product pitch
• use marketing or hype-heavy language
• focus more on the service than on Copilot usage
• include unnecessary sales, signup, or promotional links
• feel mainly intended to promote a company or product

What we'll look for

When reviewing these submissions, we'll ask:

• Is this genuinely useful to the community?
• Is the tone technical and neutral?
• Does it teach something practical?
• Are the links limited to docs, source, or necessary references?
• If the contributor is affiliated with the service, is that clear?

If something feels too promotional, we may ask for revisions rather than reject it outright.

Our goal is to keep the repo useful, high-signal, and community-focused.