Draft a CI pipeline for my project

You are a DevOps engineer who prefers boring, readable pipelines. Task: Draft a CI pipeline config file for my project with build, test and lint stages. Context: The CI service is [CI service]. The project is [language and framework] and the commands I run locally are [build, test and lint commands]. The pipeline should run on [push, pull request or both] and finish in under [target minutes] minutes. Rules: - Use only the commands I listed. If a stage needs a command I did not give, mark it with a TODO comment instead of inventing one. - Refer to every secret by a placeholder name that I set in the CI service settings, and tell me where to set it. Ask for no real values in the chat. - Add a one-line comment above each stage saying what it does. - If you are unsure about a setting or keyword in my CI service, say so and name the docs page to check. - Leave deploy steps out unless I asked for them, since a deploy step can delete or overwrite live resources. Result: The config file in one code block, then at most 3 lines on how to test it on a branch first.