···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
+70
.fluentci/.fluentci/.fluentci/CONTRIBUTING.md
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+88
.fluentci/.fluentci/.fluentci/README.md
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
88+99+## ๐ Usage
1010+1111+Quick start:
1212+1313+```ts
1414+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
1515+1616+const { pipeline } = GitLab;
1717+1818+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
1919+```
2020+2121+Or, if you want to use the predefined jobs:
2222+2323+```ts
2424+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
2525+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
2626+2727+const { fmt, lint, test } = GitLab;
2828+2929+const const pipeline = new GitlabCI()
3030+ .image("denoland/deno:alpine")
3131+ .addJob("fmt", fmt)
3232+ .addJob("lint", lint)
3333+ .addJob("test", test);
3434+3535+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
3636+```
3737+3838+It will generate the following `.gitlab-ci.yml` file:
3939+4040+```yaml
4141+# Do not edit this file directly. It is generated by Fluent GitLab CI
4242+4343+image: denoland/deno:alpine
4444+4545+fmt:
4646+ image: denoland/deno:alpine
4747+ script:
4848+ - deno fmt --check
4949+5050+lint:
5151+ image: denoland/deno:alpine
5252+ script:
5353+ - deno lint
5454+5555+test:
5656+ image: denoland/deno:alpine
5757+ script:
5858+ - deno test
5959+```
6060+6161+## ๐งช Advanced Usage
6262+6363+This package also provides a ready-to-use pipeline for
6464+[Dagger](https://dagger.io/), just run the following command on your Deno
6565+project:
6666+6767+```sh
6868+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
6969+```
7070+7171+Or, if you want to use the predefined jobs:
7272+7373+```ts
7474+import Client, { connect } from "@dagger.io/dagger";
7575+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
7676+7777+const { fmt, lint, test } = Dagger;
7878+7979+function pipeline(src = ".") {
8080+ connect(async (client: Client) => {
8181+ await fmt(client, src);
8282+ await lint(client, src);
8383+ await test(client, src);
8484+ });
8585+}
8686+8787+pipeline();
8888+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
+70
.fluentci/.fluentci/CONTRIBUTING.md
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+69
.fluentci/.fluentci/README.md
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use CI/CD Pipeline for your Deno projects.
88+99+## ๐ Usage
1010+1111+Run the following command:
1212+1313+```bash
1414+dagger run fluentci deno_pipeline
1515+```
1616+1717+Or, if you want to use it as a template:
1818+1919+```bash
2020+fluentci init -t deno
2121+```
2222+2323+This will create a `.fluentci` folder in your project.
2424+2525+Now you can run the pipeline with:
2626+2727+```bash
2828+dagger run fluentci .
2929+```
3030+3131+## Environment variables (Deno Deploy)
3232+3333+| Variable | Description | Default |
3434+| ----------------- | ------------------------- | ---------- |
3535+| DENO_PROJECT | Your project name | |
3636+| NO_STATIC | Disable static assets | `false` |
3737+| EXCLUDE | Exclude files from deploy | |
3838+| DENO_DEPLOY_TOKEN | Your Deno Deploy token | |
3939+| DENO_MAIN_SCRIPT | Your main script | `main.tsx` |
4040+4141+## Jobs
4242+4343+| Job | Description | Options |
4444+| ------ | ------------------------------ | ---------------------- |
4545+| fmt | Format your code | |
4646+| lint | Lint your code | |
4747+| test | Run your tests | `{ ignore: string[] }` |
4848+| deploy | Deploy your app to Deno Deploy | |
4949+5050+## Programmatic usage
5151+5252+You can also use this pipeline programmatically:
5353+5454+```ts
5555+import { Client, connect } from "https://esm.sh/@dagger.io/dagger@0.8.1";
5656+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
5757+5858+const { fmt, lint, test } = Dagger;
5959+6060+function pipeline(src = ".") {
6161+ connect(async (client: Client) => {
6262+ await fmt(client, src);
6363+ await lint(client, src);
6464+ await test(client, src);
6565+ });
6666+}
6767+6868+pipeline();
6969+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
88+99+## ๐ Usage
1010+1111+Quick start:
1212+1313+```ts
1414+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
1515+1616+const { pipeline } = GitLab;
1717+1818+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
1919+```
2020+2121+Or, if you want to use the predefined jobs:
2222+2323+```ts
2424+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
2525+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
2626+2727+const { fmt, lint, test } = GitLab;
2828+2929+const const pipeline = new GitlabCI()
3030+ .image("denoland/deno:alpine")
3131+ .addJob("fmt", fmt)
3232+ .addJob("lint", lint)
3333+ .addJob("test", test);
3434+3535+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
3636+```
3737+3838+It will generate the following `.gitlab-ci.yml` file:
3939+4040+```yaml
4141+# Do not edit this file directly. It is generated by Fluent GitLab CI
4242+4343+image: denoland/deno:alpine
4444+4545+fmt:
4646+ image: denoland/deno:alpine
4747+ script:
4848+ - deno fmt --check
4949+5050+lint:
5151+ image: denoland/deno:alpine
5252+ script:
5353+ - deno lint
5454+5555+test:
5656+ image: denoland/deno:alpine
5757+ script:
5858+ - deno test
5959+```
6060+6161+## ๐งช Advanced Usage
6262+6363+This package also provides a ready-to-use pipeline for
6464+[Dagger](https://dagger.io/), just run the following command on your Deno
6565+project:
6666+6767+```sh
6868+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
6969+```
7070+7171+Or, if you want to use the predefined jobs:
7272+7373+```ts
7474+import Client, { connect } from "@dagger.io/dagger";
7575+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
7676+7777+const { fmt, lint, test } = Dagger;
7878+7979+function pipeline(src = ".") {
8080+ connect(async (client: Client) => {
8181+ await fmt(client, src);
8282+ await lint(client, src);
8383+ await test(client, src);
8484+ });
8585+}
8686+8787+pipeline();
8888+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/example/.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+58
.fluentci/.fluentci/example/.fluentci/README.md
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use CI/CD Pipeline for your Deno projects.
88+99+## ๐ Usage
1010+1111+Run the following command:
1212+1313+```bash
1414+dagger run fluentci deno_pipeline
1515+```
1616+1717+Or, if you want to use it as a template:
1818+1919+```bash
2020+fluentci init -t deno
2121+```
2222+2323+This will create a `.fluentci` folder in your project.
2424+2525+Now you can run the pipeline with:
2626+2727+```bash
2828+dagger run fluentci .
2929+```
3030+3131+## Jobs
3232+3333+| Job | Description | Options |
3434+| ----- | ---------------- | ---------------------- |
3535+| fmt | Format your code | |
3636+| lint | Lint your code | |
3737+| test | Run your tests | `{ ignore: string[] }` |
3838+3939+## Programmatic usage
4040+4141+You can also use this pipeline programmatically:
4242+4343+```ts
4444+import Client, { connect } from "@dagger.io/dagger";
4545+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
4646+4747+const { fmt, lint, test } = Dagger;
4848+4949+function pipeline(src = ".") {
5050+ connect(async (client: Client) => {
5151+ await fmt(client, src);
5252+ await lint(client, src);
5353+ await test(client, src);
5454+ });
5555+}
5656+5757+pipeline();
5858+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Deno Pipeline Example
22+33+This is an example using the [Deno Pipeline](https://github.com/fluent-ci-templates/deno-pipeline).
44+55+## ๐ Usage
66+77+You need to set the following environment variables:
88+99+- `DENO_DEPLOY_TOKEN`: Your Deno Deploy token.
1010+- `DENO_PROJECT`: Your project name.
1111+1212+Then, run the following command:
1313+1414+```bash
1515+dagger run fluentci . fmt lint deploy
1616+```
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/rust-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
+70
.fluentci/CONTRIBUTING.md
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+54
.fluentci/README.md
···11+# Rust Pipeline
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+A ready-to-use CI/CD Pipeline for your Rust projects.
99+## ๐ Usage
1010+1111+Run the following command in your Rust Project:
1212+1313+```bash
1414+fluentci run rust_pipeline
1515+```
1616+1717+Or if you want to run specific jobs:
1818+1919+```bash
2020+fluentci run rust_pipeline test build
2121+```
2222+2323+2424+if you want to use it as a template:
2525+2626+```bash
2727+fluentci init -t rust
2828+```
2929+3030+This will create a `.fluentci` folder in your project.
3131+3232+Now you can run the pipeline with:
3333+3434+```bash
3535+fluentci run .
3636+```
3737+3838+## Jobs
3939+4040+| Job | Description |
4141+| ----- | ------------------ |
4242+| build | build your project |
4343+| test | Run your tests |
4444+4545+## Programmatic usage
4646+4747+You can also use this pipeline programmatically:
4848+4949+```ts
5050+import { build, test } from "https://pkg.fluentci.io/rust_pipeline@v0.6.1/mod.ts";
5151+5252+await test();
5353+await build();
5454+```
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
88+99+## ๐ Usage
1010+1111+Quick start:
1212+1313+```ts
1414+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
1515+1616+const { pipeline } = GitLab;
1717+1818+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
1919+```
2020+2121+Or, if you want to use the predefined jobs:
2222+2323+```ts
2424+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
2525+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
2626+2727+const { fmt, lint, test } = GitLab;
2828+2929+const const pipeline = new GitlabCI()
3030+ .image("denoland/deno:alpine")
3131+ .addJob("fmt", fmt)
3232+ .addJob("lint", lint)
3333+ .addJob("test", test);
3434+3535+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
3636+```
3737+3838+It will generate the following `.gitlab-ci.yml` file:
3939+4040+```yaml
4141+# Do not edit this file directly. It is generated by Fluent GitLab CI
4242+4343+image: denoland/deno:alpine
4444+4545+fmt:
4646+ image: denoland/deno:alpine
4747+ script:
4848+ - deno fmt --check
4949+5050+lint:
5151+ image: denoland/deno:alpine
5252+ script:
5353+ - deno lint
5454+5555+test:
5656+ image: denoland/deno:alpine
5757+ script:
5858+ - deno test
5959+```
6060+6161+## ๐งช Advanced Usage
6262+6363+This package also provides a ready-to-use pipeline for
6464+[Dagger](https://dagger.io/), just run the following command on your Deno
6565+project:
6666+6767+```sh
6868+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
6969+```
7070+7171+Or, if you want to use the predefined jobs:
7272+7373+```ts
7474+import Client, { connect } from "@dagger.io/dagger";
7575+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
7676+7777+const { fmt, lint, test } = Dagger;
7878+7979+function pipeline(src = ".") {
8080+ connect(async (client: Client) => {
8181+ await fmt(client, src);
8282+ await lint(client, src);
8383+ await test(client, src);
8484+ });
8585+}
8686+8787+pipeline();
8888+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/example/.fluentci/.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+69
.fluentci/example/.fluentci/.fluentci/README.md
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use CI/CD Pipeline for your Deno projects.
88+99+## ๐ Usage
1010+1111+Run the following command:
1212+1313+```bash
1414+dagger run fluentci deno_pipeline
1515+```
1616+1717+Or, if you want to use it as a template:
1818+1919+```bash
2020+fluentci init -t deno
2121+```
2222+2323+This will create a `.fluentci` folder in your project.
2424+2525+Now you can run the pipeline with:
2626+2727+```bash
2828+dagger run fluentci .
2929+```
3030+3131+## Environment variables (Deno Deploy)
3232+3333+| Variable | Description | Default |
3434+| ----------------- | ------------------------- | ---------- |
3535+| DENO_PROJECT | Your project name | |
3636+| NO_STATIC | Disable static assets | `false` |
3737+| EXCLUDE | Exclude files from deploy | |
3838+| DENO_DEPLOY_TOKEN | Your Deno Deploy token | |
3939+| DENO_MAIN_SCRIPT | Your main script | `main.tsx` |
4040+4141+## Jobs
4242+4343+| Job | Description | Options |
4444+| ------ | ------------------------------ | ---------------------- |
4545+| fmt | Format your code | |
4646+| lint | Lint your code | |
4747+| test | Run your tests | `{ ignore: string[] }` |
4848+| deploy | Deploy your app to Deno Deploy | |
4949+5050+## Programmatic usage
5151+5252+You can also use this pipeline programmatically:
5353+5454+```ts
5555+import { Client, connect } from "https://esm.sh/@dagger.io/dagger@0.8.1";
5656+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
5757+5858+const { fmt, lint, test } = Dagger;
5959+6060+function pipeline(src = ".") {
6161+ connect(async (client: Client) => {
6262+ await fmt(client, src);
6363+ await lint(client, src);
6464+ await test(client, src);
6565+ });
6666+}
6767+6868+pipeline();
6969+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
22+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
33+{
44+ "name": "Debian",
55+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
66+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
77+ "features": {
88+ "ghcr.io/devcontainers/features/github-cli:1": {},
99+ "ghcr.io/devcontainers/features/nix:1": {}
1010+ },
1111+1212+ // Features to add to the dev container. More info: https://containers.dev/features.
1313+ // "features": {},
1414+1515+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
1616+ // "forwardPorts": [],
1717+1818+ // Use 'postCreateCommand' to run commands after the container is created.
1919+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
2020+ // Configure tool-specific properties.
2121+ // "customizations": {},
2222+2323+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
2424+ // "remoteUser": "root"
2525+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
88+99+## ๐ Usage
1010+1111+Quick start:
1212+1313+```ts
1414+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
1515+1616+const { pipeline } = GitLab;
1717+1818+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
1919+```
2020+2121+Or, if you want to use the predefined jobs:
2222+2323+```ts
2424+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
2525+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
2626+2727+const { fmt, lint, test } = GitLab;
2828+2929+const const pipeline = new GitlabCI()
3030+ .image("denoland/deno:alpine")
3131+ .addJob("fmt", fmt)
3232+ .addJob("lint", lint)
3333+ .addJob("test", test);
3434+3535+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
3636+```
3737+3838+It will generate the following `.gitlab-ci.yml` file:
3939+4040+```yaml
4141+# Do not edit this file directly. It is generated by Fluent GitLab CI
4242+4343+image: denoland/deno:alpine
4444+4545+fmt:
4646+ image: denoland/deno:alpine
4747+ script:
4848+ - deno fmt --check
4949+5050+lint:
5151+ image: denoland/deno:alpine
5252+ script:
5353+ - deno lint
5454+5555+test:
5656+ image: denoland/deno:alpine
5757+ script:
5858+ - deno test
5959+```
6060+6161+## ๐งช Advanced Usage
6262+6363+This package also provides a ready-to-use pipeline for
6464+[Dagger](https://dagger.io/), just run the following command on your Deno
6565+project:
6666+6767+```sh
6868+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
6969+```
7070+7171+Or, if you want to use the predefined jobs:
7272+7373+```ts
7474+import Client, { connect } from "@dagger.io/dagger";
7575+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
7676+7777+const { fmt, lint, test } = Dagger;
7878+7979+function pipeline(src = ".") {
8080+ connect(async (client: Client) => {
8181+ await fmt(client, src);
8282+ await lint(client, src);
8383+ await test(client, src);
8484+ });
8585+}
8686+8787+pipeline();
8888+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
···11+# Deno Pipeline
22+33+[](https://deno.land/x/deno_pipeline)
44+
55+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
66+77+A ready-to-use CI/CD Pipeline for your Deno projects.
88+99+## ๐ Usage
1010+1111+Run the following command:
1212+1313+```bash
1414+dagger run fluentci deno_pipeline
1515+```
1616+1717+Or, if you want to use it as a template:
1818+1919+```bash
2020+fluentci init -t deno
2121+```
2222+2323+This will create a `.fluentci` folder in your project.
2424+2525+Now you can run the pipeline with:
2626+2727+```bash
2828+dagger run fluentci .
2929+```
3030+3131+## Jobs
3232+3333+| Job | Description | Options |
3434+| ----- | ---------------- | ---------------------- |
3535+| fmt | Format your code | |
3636+| lint | Lint your code | |
3737+| test | Run your tests | `{ ignore: string[] }` |
3838+3939+## Programmatic usage
4040+4141+You can also use this pipeline programmatically:
4242+4343+```ts
4444+import Client, { connect } from "@dagger.io/dagger";
4545+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
4646+4747+const { fmt, lint, test } = Dagger;
4848+4949+function pipeline(src = ".") {
5050+ connect(async (client: Client) => {
5151+ await fmt(client, src);
5252+ await lint(client, src);
5353+ await test(client, src);
5454+ });
5555+}
5656+5757+pipeline();
5858+```
···11+{
22+ "importMap": "import_map.json",
33+ "tasks": {
44+ "esm:add": "deno run -A https://esm.sh/v128 add",
55+ "esm:update": "deno run -A https://esm.sh/v128 update",
66+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
77+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
88+ }
99+}
···11+# Deno Pipeline Example
22+33+This is an example using the [Deno Pipeline](https://github.com/fluent-ci-templates/deno-pipeline).
44+55+## ๐ Usage
66+77+You need to set the following environment variables:
88+99+- `DENO_DEPLOY_TOKEN`: Your Deno Deploy token.
1010+- `DENO_PROJECT`: Your project name.
1111+1212+Then, run the following command:
1313+1414+```bash
1515+dagger run fluentci . fmt lint deploy
1616+```
···11+# Contributor Covenant Code of Conduct
22+33+## Our Pledge
44+55+We as members, contributors, and leaders pledge to make participation in our
66+community a harassment-free experience for everyone, regardless of age, body
77+size, visible or invisible disability, ethnicity, sex characteristics, gender
88+identity and expression, level of experience, education, socio-economic status,
99+nationality, personal appearance, race, caste, color, religion, or sexual
1010+identity and orientation.
1111+1212+We pledge to act and interact in ways that contribute to an open, welcoming,
1313+diverse, inclusive, and healthy community.
1414+1515+## Our Standards
1616+1717+Examples of behavior that contributes to a positive environment for our
1818+community include:
1919+2020+- Demonstrating empathy and kindness toward other people
2121+- Being respectful of differing opinions, viewpoints, and experiences
2222+- Giving and gracefully accepting constructive feedback
2323+- Accepting responsibility and apologizing to those affected by our mistakes,
2424+ and learning from the experience
2525+- Focusing on what is best not just for us as individuals, but for the overall
2626+ community
2727+2828+Examples of unacceptable behavior include:
2929+3030+- The use of sexualized language or imagery, and sexual attention or advances of
3131+ any kind
3232+- Trolling, insulting or derogatory comments, and personal or political attacks
3333+- Public or private harassment
3434+- Publishing others' private information, such as a physical or email address,
3535+ without their explicit permission
3636+- Other conduct which could reasonably be considered inappropriate in a
3737+ professional setting
3838+3939+## Enforcement Responsibilities
4040+4141+Community leaders are responsible for clarifying and enforcing our standards of
4242+acceptable behavior and will take appropriate and fair corrective action in
4343+response to any behavior that they deem inappropriate, threatening, offensive,
4444+or harmful.
4545+4646+Community leaders have the right and responsibility to remove, edit, or reject
4747+comments, commits, code, wiki edits, issues, and other contributions that are
4848+not aligned to this Code of Conduct, and will communicate reasons for moderation
4949+decisions when appropriate.
5050+5151+## Scope
5252+5353+This Code of Conduct applies within all community spaces, and also applies when
5454+an individual is officially representing the community in public spaces.
5555+Examples of representing our community include using an official e-mail address,
5656+posting via an official social media account, or acting as an appointed
5757+representative at an online or offline event.
5858+5959+## Enforcement
6060+6161+Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262+reported to the community leaders responsible for enforcement at
6363+[GitHub Issues](https://github.com/fluent-ci-templates/rust-pipeline/issues).
6464+All complaints will be reviewed and investigated promptly and fairly.
6565+6666+All community leaders are obligated to respect the privacy and security of the
6767+reporter of any incident.
6868+6969+## Enforcement Guidelines
7070+7171+Community leaders will follow these Community Impact Guidelines in determining
7272+the consequences for any action they deem in violation of this Code of Conduct:
7373+7474+### 1. Correction
7575+7676+**Community Impact**: Use of inappropriate language or other behavior deemed
7777+unprofessional or unwelcome in the community.
7878+7979+**Consequence**: A private, written warning from community leaders, providing
8080+clarity around the nature of the violation and an explanation of why the
8181+behavior was inappropriate. A public apology may be requested.
8282+8383+### 2. Warning
8484+8585+**Community Impact**: A violation through a single incident or series of
8686+actions.
8787+8888+**Consequence**: A warning with consequences for continued behavior. No
8989+interaction with the people involved, including unsolicited interaction with
9090+those enforcing the Code of Conduct, for a specified period of time. This
9191+includes avoiding interactions in community spaces as well as external channels
9292+like social media. Violating these terms may lead to a temporary or permanent
9393+ban.
9494+9595+### 3. Temporary Ban
9696+9797+**Community Impact**: A serious violation of community standards, including
9898+sustained inappropriate behavior.
9999+100100+**Consequence**: A temporary ban from any sort of interaction or public
101101+communication with the community for a specified period of time. No public or
102102+private interaction with the people involved, including unsolicited interaction
103103+with those enforcing the Code of Conduct, is allowed during this period.
104104+Violating these terms may lead to a permanent ban.
105105+106106+### 4. Permanent Ban
107107+108108+**Community Impact**: Demonstrating a pattern of violation of community
109109+standards, including sustained inappropriate behavior, harassment of an
110110+individual, or aggression toward or disparagement of classes of individuals.
111111+112112+**Consequence**: A permanent ban from any sort of public interaction within the
113113+community.
114114+115115+## Attribution
116116+117117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118+version 2.1, available at
119119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120120+121121+Community Impact Guidelines were inspired by
122122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123123+124124+For answers to common questions about this code of conduct, see the FAQ at
125125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126126+[https://www.contributor-covenant.org/translations][translations].
127127+128128+[homepage]: https://www.contributor-covenant.org
129129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130130+[Mozilla CoC]: https://github.com/mozilla/diversity
131131+[FAQ]: https://www.contributor-covenant.org/faq
132132+[translations]: https://www.contributor-covenant.org/translations
+70
.fluentci/example/.fluentci/CONTRIBUTING.md
···11+# Contributing Guidelines
22+33+Thank you for your interest in contributing to our project. Whether it's a bug
44+report, new feature, correction, or additional documentation, we greatly value
55+feedback and contributions from our community.
66+77+Please read through this document before submitting any issues or pull requests
88+to ensure we have all the necessary information to effectively respond to your
99+bug report or contribution.
1010+1111+## Reporting Bugs/Feature Requests
1212+1313+We welcome you to use the GitHub issue tracker to report bugs or suggest
1414+features.
1515+1616+When filing an issue, please check existing open, or recently closed, issues to
1717+make sure somebody else hasn't already reported the issue. Please try to include
1818+as much information as you can. Details like these are incredibly useful:
1919+2020+- A reproducible test case or series of steps
2121+- The version of our code being used
2222+- Any modifications you've made relevant to the bug
2323+- Anything unusual about your environment or deployment
2424+2525+## Contributing via Pull Requests
2626+2727+Contributions via pull requests are much appreciated. Before sending us a pull
2828+request, please ensure that:
2929+3030+1. You are working against the latest source on the _master_ branch.
3131+2. You check existing open, and recently merged, pull requests to make sure
3232+ someone else hasn't addressed the problem already.
3333+3. You open an issue to discuss any significant work - we would hate for your
3434+ time to be wasted.
3535+3636+To send us a pull request, please:
3737+3838+1. Fork the repository.
3939+2. Modify the source; please focus on the specific change you are contributing.
4040+ If you also reformat all the code, it will be hard for us to focus on your
4141+ change.
4242+3. Ensure local tests pass.
4343+4. Commit to your fork using clear commit messages.
4444+5. Send us a pull request, answering any default questions in the pull request
4545+ interface.
4646+6. Pay attention to any automated CI failures reported in the pull request, and
4747+ stay involved in the conversation.
4848+4949+GitHub provides additional document on
5050+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
5151+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
5252+5353+## Finding contributions to work on
5454+5555+Looking at the existing issues is a great way to find something to contribute
5656+on. As our projects, by default, use the default GitHub issue labels
5757+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
5858+'help wanted' issues is a great place to start.
5959+6060+## Code of Conduct
6161+6262+This project has adopted the
6363+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
6464+available at
6565+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
6666+6767+## Licensing
6868+6969+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
7070+confirm the licensing of your contribution.
+19
.fluentci/example/.fluentci/LICENSE
···11+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
22+33+Permission is hereby granted, free of charge, to any person obtaining a copy
44+of this software and associated documentation files (the "Software"), to deal
55+in the Software without restriction, including without limitation the rights
66+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
77+copies of the Software, and to permit persons to whom the Software is
88+furnished to do so, subject to the following conditions:
99+1010+The above copyright notice and this permission notice shall be included in all
1111+copies or substantial portions of the Software.
1212+1313+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
1414+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
1515+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1616+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1717+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
1818+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
1919+SOFTWARE.
+61
.fluentci/example/.fluentci/README.md
···11+# Rust Pipeline
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+A ready-to-use CI/CD Pipeline for your Rust projects.
99+## ๐ Usage
1010+1111+Run the following command in your Rust Project:
1212+1313+```bash
1414+fluentci run rust_pipeline
1515+```
1616+1717+Or if you want to run specific jobs:
1818+1919+```bash
2020+fluentci run rust_pipeline test build
2121+```
2222+2323+2424+if you want to use it as a template:
2525+2626+```bash
2727+fluentci init -t rust
2828+```
2929+3030+This will create a `.fluentci` folder in your project.
3131+3232+Now you can run the pipeline with:
3333+3434+```bash
3535+fluentci run .
3636+```
3737+3838+## Jobs
3939+4040+| Job | Description |
4141+| ----- | ------------------ |
4242+| build | build your project |
4343+| test | Run your tests |
4444+4545+## Programmatic usage
4646+4747+You can also use this pipeline programmatically:
4848+4949+```ts
5050+import Client, { connect } from "https://sdk.fluentci.io/v0.1.9/mod.ts";
5151+import { build, test } from "https://pkg.fluentci.io/rust_pipeline@v0.5.2/mod.ts";
5252+5353+function pipeline(src = ".") {
5454+ connect(async (client: Client) => {
5555+ await test(client, src);
5656+ await build(client, src);
5757+ });
5858+}
5959+6060+pipeline();
6161+```
···11+# This file is automatically @generated by Cargo.
22+# It is not intended for manual editing.
33+version = 3
44+55+[[package]]
66+name = "example"
77+version = "0.1.0"
+8
.fluentci/example/.fluentci/example/Cargo.toml
···11+[package]
22+name = "example"
33+version = "0.1.0"
44+edition = "2021"
55+66+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
77+88+[dependencies]
···11+export * from "./src/dagger/index.ts";
22+export * as queries from "./src/dagger/queries.ts";
33+export { schema } from "./src/dagger/schema.ts";
+8
.fluentci/example/.fluentci/schema.graphql
···11+### This file was generated by Nexus Schema
22+### Do not make changes to this file directly
33+44+55+type Query {
66+ build(src: String!): String
77+ test(src: String!): String
88+}
+39
.fluentci/example/.fluentci/src/aws/README.md
···11+# AWS CodePipeline
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+The following command will generate a `buildspec.yml` file in your project:
99+1010+```bash
1111+fluentci ac init -t rust_pipeline
1212+```
1313+1414+Generated file:
1515+1616+```yaml
1717+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_aws_codepipeline
1818+1919+version: 0.2
2020+phases:
2121+ install:
2222+ commands:
2323+ - curl -fsSL https://deno.land/x/install/install.sh | sh
2424+ - export DENO_INSTALL="$HOME/.deno"
2525+ - export PATH="$DENO_INSTALL/bin:$PATH"
2626+ - deno install -A -r https://cli.fluentci.io -n fluentci
2727+ - curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
2828+ - mv bin/dagger /usr/local/bin
2929+ - dagger version
3030+ build:
3131+ commands:
3232+ - fluentci run rust_pipeline test build
3333+ post_build:
3434+ commands:
3535+ - echo Build completed on `date`
3636+3737+```
3838+3939+Feel free to edit the template generator at `.fluentci/src/aws/config.ts` to your needs.
···11+# Github Actions
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+The following command will generate a `.github/workflows/tests.yml` file in your project:
99+1010+```bash
1111+fluentci gh init -t rust_pipeline
1212+```
1313+1414+Or, if you already have a `.fluentci` folder (generated from `fluentci init -t rust`) in your project:
1515+1616+```bash
1717+fluentci gh init
1818+```
1919+2020+Generated file:
2121+2222+```yaml
2323+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_github_actions
2424+2525+name: Test
2626+on:
2727+ push:
2828+ branches:
2929+ - main
3030+jobs:
3131+ test:
3232+ runs-on: ubuntu-latest
3333+ steps:
3434+ - uses: actions/checkout@v2
3535+ - uses: denoland/setup-deno@v1
3636+ with:
3737+ deno-version: v1.37
3838+ - name: Setup Fluent CI CLI
3939+ run: deno install -A -r https://cli.fluentci.io -n fluentci
4040+ - name: Setup Dagger
4141+ run: |
4242+ curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
4343+ sudo mv bin/dagger /usr/local/bin
4444+ dagger version
4545+ - name: Run Tests and Build
4646+ run: fluentci run rust_pipeline test build
4747+4848+```
4949+5050+Feel free to edit the template generator at `.fluentci/src/github/config.ts` to your needs.
···11+# This file is automatically @generated by Cargo.
22+# It is not intended for manual editing.
33+version = 3
44+55+[[package]]
66+name = "example"
77+version = "0.1.0"
+8
.fluentci/example/Cargo.toml
···11+[package]
22+name = "example"
33+version = "0.1.0"
44+edition = "2021"
55+66+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
77+88+[dependencies]
···11+export * from "./src/dagger/index.ts";
22+export * as queries from "./src/dagger/queries.ts";
33+export { schema } from "./src/dagger/schema.ts";
+8
.fluentci/schema.graphql
···11+### This file was generated by Nexus Schema
22+### Do not make changes to this file directly
33+44+55+type Query {
66+ build(src: String!): String
77+ test(src: String!): String
88+}
+39
.fluentci/src/aws/README.md
···11+# AWS CodePipeline
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+The following command will generate a `buildspec.yml` file in your project:
99+1010+```bash
1111+fluentci ac init -t rust_pipeline
1212+```
1313+1414+Generated file:
1515+1616+```yaml
1717+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_aws_codepipeline
1818+1919+version: 0.2
2020+phases:
2121+ install:
2222+ commands:
2323+ - curl -fsSL https://deno.land/x/install/install.sh | sh
2424+ - export DENO_INSTALL="$HOME/.deno"
2525+ - export PATH="$DENO_INSTALL/bin:$PATH"
2626+ - deno install -A -r https://cli.fluentci.io -n fluentci
2727+ - curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
2828+ - mv bin/dagger /usr/local/bin
2929+ - dagger version
3030+ build:
3131+ commands:
3232+ - fluentci run rust_pipeline test build
3333+ post_build:
3434+ commands:
3535+ - echo Build completed on `date`
3636+3737+```
3838+3939+Feel free to edit the template generator at `.fluentci/src/aws/config.ts` to your needs.
···11+# Github Actions
22+33+[](https://pkg.fluentci.io/rust_pipeline)
44+[](https://deno.land/x/rust_pipeline)
55+
66+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
77+88+The following command will generate a `.github/workflows/tests.yml` file in your project:
99+1010+```bash
1111+fluentci gh init -t rust_pipeline
1212+```
1313+1414+Or, if you already have a `.fluentci` folder (generated from `fluentci init -t rust`) in your project:
1515+1616+```bash
1717+fluentci gh init
1818+```
1919+2020+Generated file:
2121+2222+```yaml
2323+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_github_actions
2424+2525+name: Test
2626+on:
2727+ push:
2828+ branches:
2929+ - main
3030+jobs:
3131+ test:
3232+ runs-on: ubuntu-latest
3333+ steps:
3434+ - uses: actions/checkout@v2
3535+ - uses: denoland/setup-deno@v1
3636+ with:
3737+ deno-version: v1.37
3838+ - name: Setup Fluent CI CLI
3939+ run: deno install -A -r https://cli.fluentci.io -n fluentci
4040+ - name: Setup Dagger
4141+ run: |
4242+ curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
4343+ sudo mv bin/dagger /usr/local/bin
4444+ dagger version
4545+ - name: Run Tests and Build
4646+ run: fluentci run rust_pipeline test build
4747+4848+```
4949+5050+Feel free to edit the template generator at `.fluentci/src/github/config.ts` to your needs.