···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
8+9+## ๐ Usage
10+11+Quick start:
12+13+```ts
14+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
15+16+const { pipeline } = GitLab;
17+18+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
19+```
20+21+Or, if you want to use the predefined jobs:
22+23+```ts
24+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
25+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
26+27+const { fmt, lint, test } = GitLab;
28+29+const const pipeline = new GitlabCI()
30+ .image("denoland/deno:alpine")
31+ .addJob("fmt", fmt)
32+ .addJob("lint", lint)
33+ .addJob("test", test);
34+35+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
36+```
37+38+It will generate the following `.gitlab-ci.yml` file:
39+40+```yaml
41+# Do not edit this file directly. It is generated by Fluent GitLab CI
42+43+image: denoland/deno:alpine
44+45+fmt:
46+ image: denoland/deno:alpine
47+ script:
48+ - deno fmt --check
49+50+lint:
51+ image: denoland/deno:alpine
52+ script:
53+ - deno lint
54+55+test:
56+ image: denoland/deno:alpine
57+ script:
58+ - deno test
59+```
60+61+## ๐งช Advanced Usage
62+63+This package also provides a ready-to-use pipeline for
64+[Dagger](https://dagger.io/), just run the following command on your Deno
65+project:
66+67+```sh
68+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
69+```
70+71+Or, if you want to use the predefined jobs:
72+73+```ts
74+import Client, { connect } from "@dagger.io/dagger";
75+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
76+77+const { fmt, lint, test } = Dagger;
78+79+function pipeline(src = ".") {
80+ connect(async (client: Client) => {
81+ await fmt(client, src);
82+ await lint(client, src);
83+ await test(client, src);
84+ });
85+}
86+87+pipeline();
88+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
8+9+## ๐ Usage
10+11+Quick start:
12+13+```ts
14+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
15+16+const { pipeline } = GitLab;
17+18+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
19+```
20+21+Or, if you want to use the predefined jobs:
22+23+```ts
24+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
25+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
26+27+const { fmt, lint, test } = GitLab;
28+29+const const pipeline = new GitlabCI()
30+ .image("denoland/deno:alpine")
31+ .addJob("fmt", fmt)
32+ .addJob("lint", lint)
33+ .addJob("test", test);
34+35+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
36+```
37+38+It will generate the following `.gitlab-ci.yml` file:
39+40+```yaml
41+# Do not edit this file directly. It is generated by Fluent GitLab CI
42+43+image: denoland/deno:alpine
44+45+fmt:
46+ image: denoland/deno:alpine
47+ script:
48+ - deno fmt --check
49+50+lint:
51+ image: denoland/deno:alpine
52+ script:
53+ - deno lint
54+55+test:
56+ image: denoland/deno:alpine
57+ script:
58+ - deno test
59+```
60+61+## ๐งช Advanced Usage
62+63+This package also provides a ready-to-use pipeline for
64+[Dagger](https://dagger.io/), just run the following command on your Deno
65+project:
66+67+```sh
68+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
69+```
70+71+Or, if you want to use the predefined jobs:
72+73+```ts
74+import Client, { connect } from "@dagger.io/dagger";
75+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
76+77+const { fmt, lint, test } = Dagger;
78+79+function pipeline(src = ".") {
80+ connect(async (client: Client) => {
81+ await fmt(client, src);
82+ await lint(client, src);
83+ await test(client, src);
84+ });
85+}
86+87+pipeline();
88+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/.fluentci/example/.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use CI/CD Pipeline for your Deno projects.
8+9+## ๐ Usage
10+11+Run the following command:
12+13+```bash
14+dagger run fluentci deno_pipeline
15+```
16+17+Or, if you want to use it as a template:
18+19+```bash
20+fluentci init -t deno
21+```
22+23+This will create a `.fluentci` folder in your project.
24+25+Now you can run the pipeline with:
26+27+```bash
28+dagger run fluentci .
29+```
30+31+## Jobs
32+33+| Job | Description | Options |
34+| ----- | ---------------- | ---------------------- |
35+| fmt | Format your code | |
36+| lint | Lint your code | |
37+| test | Run your tests | `{ ignore: string[] }` |
38+39+## Programmatic usage
40+41+You can also use this pipeline programmatically:
42+43+```ts
44+import Client, { connect } from "@dagger.io/dagger";
45+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
46+47+const { fmt, lint, test } = Dagger;
48+49+function pipeline(src = ".") {
50+ connect(async (client: Client) => {
51+ await fmt(client, src);
52+ await lint(client, src);
53+ await test(client, src);
54+ });
55+}
56+57+pipeline();
58+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Deno Pipeline Example
2+3+This is an example using the [Deno Pipeline](https://github.com/fluent-ci-templates/deno-pipeline).
4+5+## ๐ Usage
6+7+You need to set the following environment variables:
8+9+- `DENO_DEPLOY_TOKEN`: Your Deno Deploy token.
10+- `DENO_PROJECT`: Your project name.
11+12+Then, run the following command:
13+14+```bash
15+dagger run fluentci . fmt lint deploy
16+```
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/rust-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Rust Pipeline
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+A ready-to-use CI/CD Pipeline for your Rust projects.
9+## ๐ Usage
10+11+Run the following command in your Rust Project:
12+13+```bash
14+fluentci run rust_pipeline
15+```
16+17+Or if you want to run specific jobs:
18+19+```bash
20+fluentci run rust_pipeline test build
21+```
22+23+24+if you want to use it as a template:
25+26+```bash
27+fluentci init -t rust
28+```
29+30+This will create a `.fluentci` folder in your project.
31+32+Now you can run the pipeline with:
33+34+```bash
35+fluentci run .
36+```
37+38+## Jobs
39+40+| Job | Description |
41+| ----- | ------------------ |
42+| build | build your project |
43+| test | Run your tests |
44+45+## Programmatic usage
46+47+You can also use this pipeline programmatically:
48+49+```ts
50+import { build, test } from "https://pkg.fluentci.io/rust_pipeline@v0.6.1/mod.ts";
51+52+await test();
53+await build();
54+```
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
8+9+## ๐ Usage
10+11+Quick start:
12+13+```ts
14+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
15+16+const { pipeline } = GitLab;
17+18+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
19+```
20+21+Or, if you want to use the predefined jobs:
22+23+```ts
24+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
25+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
26+27+const { fmt, lint, test } = GitLab;
28+29+const const pipeline = new GitlabCI()
30+ .image("denoland/deno:alpine")
31+ .addJob("fmt", fmt)
32+ .addJob("lint", lint)
33+ .addJob("test", test);
34+35+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
36+```
37+38+It will generate the following `.gitlab-ci.yml` file:
39+40+```yaml
41+# Do not edit this file directly. It is generated by Fluent GitLab CI
42+43+image: denoland/deno:alpine
44+45+fmt:
46+ image: denoland/deno:alpine
47+ script:
48+ - deno fmt --check
49+50+lint:
51+ image: denoland/deno:alpine
52+ script:
53+ - deno lint
54+55+test:
56+ image: denoland/deno:alpine
57+ script:
58+ - deno test
59+```
60+61+## ๐งช Advanced Usage
62+63+This package also provides a ready-to-use pipeline for
64+[Dagger](https://dagger.io/), just run the following command on your Deno
65+project:
66+67+```sh
68+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
69+```
70+71+Or, if you want to use the predefined jobs:
72+73+```ts
74+import Client, { connect } from "@dagger.io/dagger";
75+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
76+77+const { fmt, lint, test } = Dagger;
78+79+function pipeline(src = ".") {
80+ connect(async (client: Client) => {
81+ await fmt(client, src);
82+ await lint(client, src);
83+ await test(client, src);
84+ });
85+}
86+87+pipeline();
88+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/example/.fluentci/.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+// README at: https://github.com/devcontainers/templates/tree/main/src/debian
3+{
4+ "name": "Debian",
5+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
6+ "image": "mcr.microsoft.com/devcontainers/base:bullseye",
7+ "features": {
8+ "ghcr.io/devcontainers/features/github-cli:1": {},
9+ "ghcr.io/devcontainers/features/nix:1": {}
10+ },
11+12+ // Features to add to the dev container. More info: https://containers.dev/features.
13+ // "features": {},
14+15+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
16+ // "forwardPorts": [],
17+18+ // Use 'postCreateCommand' to run commands after the container is created.
19+ "postCreateCommand": "nix develop --experimental-features \"nix-command flakes\""
20+ // Configure tool-specific properties.
21+ // "customizations": {},
22+23+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
24+ // "remoteUser": "root"
25+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use GitLab CI Pipeline and Jobs for your Deno projects.
8+9+## ๐ Usage
10+11+Quick start:
12+13+```ts
14+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
15+16+const { pipeline } = GitLab;
17+18+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
19+```
20+21+Or, if you want to use the predefined jobs:
22+23+```ts
24+import { GitlabCI } from "https://deno.land/x/fluent_gitlab_ci/mod.ts";
25+import { GitLab } from "https://deno.land/x/deno_pipeline/mod.ts";
26+27+const { fmt, lint, test } = GitLab;
28+29+const const pipeline = new GitlabCI()
30+ .image("denoland/deno:alpine")
31+ .addJob("fmt", fmt)
32+ .addJob("lint", lint)
33+ .addJob("test", test);
34+35+pipeline.write(); // Write the pipeline to the file .gitlab-ci.yml
36+```
37+38+It will generate the following `.gitlab-ci.yml` file:
39+40+```yaml
41+# Do not edit this file directly. It is generated by Fluent GitLab CI
42+43+image: denoland/deno:alpine
44+45+fmt:
46+ image: denoland/deno:alpine
47+ script:
48+ - deno fmt --check
49+50+lint:
51+ image: denoland/deno:alpine
52+ script:
53+ - deno lint
54+55+test:
56+ image: denoland/deno:alpine
57+ script:
58+ - deno test
59+```
60+61+## ๐งช Advanced Usage
62+63+This package also provides a ready-to-use pipeline for
64+[Dagger](https://dagger.io/), just run the following command on your Deno
65+project:
66+67+```sh
68+dagger run deno run -A https://deno.land/x/deno_pipeline/ci.ts
69+```
70+71+Or, if you want to use the predefined jobs:
72+73+```ts
74+import Client, { connect } from "@dagger.io/dagger";
75+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
76+77+const { fmt, lint, test } = Dagger;
78+79+function pipeline(src = ".") {
80+ connect(async (client: Client) => {
81+ await fmt(client, src);
82+ await lint(client, src);
83+ await test(client, src);
84+ });
85+}
86+87+pipeline();
88+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/deno-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Deno Pipeline
2+3+[](https://deno.land/x/deno_pipeline)
4+
5+[](https://codecov.io/gh/fluent-ci-templates/deno-pipeline)
6+7+A ready-to-use CI/CD Pipeline for your Deno projects.
8+9+## ๐ Usage
10+11+Run the following command:
12+13+```bash
14+dagger run fluentci deno_pipeline
15+```
16+17+Or, if you want to use it as a template:
18+19+```bash
20+fluentci init -t deno
21+```
22+23+This will create a `.fluentci` folder in your project.
24+25+Now you can run the pipeline with:
26+27+```bash
28+dagger run fluentci .
29+```
30+31+## Jobs
32+33+| Job | Description | Options |
34+| ----- | ---------------- | ---------------------- |
35+| fmt | Format your code | |
36+| lint | Lint your code | |
37+| test | Run your tests | `{ ignore: string[] }` |
38+39+## Programmatic usage
40+41+You can also use this pipeline programmatically:
42+43+```ts
44+import Client, { connect } from "@dagger.io/dagger";
45+import { Dagger } from "https://deno.land/x/deno_pipeline/mod.ts";
46+47+const { fmt, lint, test } = Dagger;
48+49+function pipeline(src = ".") {
50+ connect(async (client: Client) => {
51+ await fmt(client, src);
52+ await lint(client, src);
53+ await test(client, src);
54+ });
55+}
56+57+pipeline();
58+```
···1+{
2+ "importMap": "import_map.json",
3+ "tasks": {
4+ "esm:add": "deno run -A https://esm.sh/v128 add",
5+ "esm:update": "deno run -A https://esm.sh/v128 update",
6+ "esm:remove": "deno run -A https://esm.sh/v128 remove",
7+ "ci:dagger": "dagger run deno run -A src/dagger/runner.ts"
8+ }
9+}
···1+# Deno Pipeline Example
2+3+This is an example using the [Deno Pipeline](https://github.com/fluent-ci-templates/deno-pipeline).
4+5+## ๐ Usage
6+7+You need to set the following environment variables:
8+9+- `DENO_DEPLOY_TOKEN`: Your Deno Deploy token.
10+- `DENO_PROJECT`: Your project name.
11+12+Then, run the following command:
13+14+```bash
15+dagger run fluentci . fmt lint deploy
16+```
···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/fluent-ci-templates/rust-pipeline/issues).
64+All complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
.fluentci/example/.fluentci/LICENSE
···0000000000000000000
···1+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@aol.com>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
···1+# Rust Pipeline
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+A ready-to-use CI/CD Pipeline for your Rust projects.
9+## ๐ Usage
10+11+Run the following command in your Rust Project:
12+13+```bash
14+fluentci run rust_pipeline
15+```
16+17+Or if you want to run specific jobs:
18+19+```bash
20+fluentci run rust_pipeline test build
21+```
22+23+24+if you want to use it as a template:
25+26+```bash
27+fluentci init -t rust
28+```
29+30+This will create a `.fluentci` folder in your project.
31+32+Now you can run the pipeline with:
33+34+```bash
35+fluentci run .
36+```
37+38+## Jobs
39+40+| Job | Description |
41+| ----- | ------------------ |
42+| build | build your project |
43+| test | Run your tests |
44+45+## Programmatic usage
46+47+You can also use this pipeline programmatically:
48+49+```ts
50+import Client, { connect } from "https://sdk.fluentci.io/v0.1.9/mod.ts";
51+import { build, test } from "https://pkg.fluentci.io/rust_pipeline@v0.5.2/mod.ts";
52+53+function pipeline(src = ".") {
54+ connect(async (client: Client) => {
55+ await test(client, src);
56+ await build(client, src);
57+ });
58+}
59+60+pipeline();
61+```
···1+# This file is automatically @generated by Cargo.
2+# It is not intended for manual editing.
3+version = 3
4+5+[[package]]
6+name = "example"
7+version = "0.1.0"
+8
.fluentci/example/.fluentci/example/Cargo.toml
···00000000
···1+[package]
2+name = "example"
3+version = "0.1.0"
4+edition = "2021"
5+6+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
7+8+[dependencies]
···1+export * from "./src/dagger/index.ts";
2+export * as queries from "./src/dagger/queries.ts";
3+export { schema } from "./src/dagger/schema.ts";
+8
.fluentci/example/.fluentci/schema.graphql
···00000000
···1+### This file was generated by Nexus Schema
2+### Do not make changes to this file directly
3+4+5+type Query {
6+ build(src: String!): String
7+ test(src: String!): String
8+}
+39
.fluentci/example/.fluentci/src/aws/README.md
···000000000000000000000000000000000000000
···1+# AWS CodePipeline
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+The following command will generate a `buildspec.yml` file in your project:
9+10+```bash
11+fluentci ac init -t rust_pipeline
12+```
13+14+Generated file:
15+16+```yaml
17+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_aws_codepipeline
18+19+version: 0.2
20+phases:
21+ install:
22+ commands:
23+ - curl -fsSL https://deno.land/x/install/install.sh | sh
24+ - export DENO_INSTALL="$HOME/.deno"
25+ - export PATH="$DENO_INSTALL/bin:$PATH"
26+ - deno install -A -r https://cli.fluentci.io -n fluentci
27+ - curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
28+ - mv bin/dagger /usr/local/bin
29+ - dagger version
30+ build:
31+ commands:
32+ - fluentci run rust_pipeline test build
33+ post_build:
34+ commands:
35+ - echo Build completed on `date`
36+37+```
38+39+Feel free to edit the template generator at `.fluentci/src/aws/config.ts` to your needs.
···1+# Github Actions
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+The following command will generate a `.github/workflows/tests.yml` file in your project:
9+10+```bash
11+fluentci gh init -t rust_pipeline
12+```
13+14+Or, if you already have a `.fluentci` folder (generated from `fluentci init -t rust`) in your project:
15+16+```bash
17+fluentci gh init
18+```
19+20+Generated file:
21+22+```yaml
23+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_github_actions
24+25+name: Test
26+on:
27+ push:
28+ branches:
29+ - main
30+jobs:
31+ test:
32+ runs-on: ubuntu-latest
33+ steps:
34+ - uses: actions/checkout@v2
35+ - uses: denoland/setup-deno@v1
36+ with:
37+ deno-version: v1.37
38+ - name: Setup Fluent CI CLI
39+ run: deno install -A -r https://cli.fluentci.io -n fluentci
40+ - name: Setup Dagger
41+ run: |
42+ curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
43+ sudo mv bin/dagger /usr/local/bin
44+ dagger version
45+ - name: Run Tests and Build
46+ run: fluentci run rust_pipeline test build
47+48+```
49+50+Feel free to edit the template generator at `.fluentci/src/github/config.ts` to your needs.
···1+# This file is automatically @generated by Cargo.
2+# It is not intended for manual editing.
3+version = 3
4+5+[[package]]
6+name = "example"
7+version = "0.1.0"
+8
.fluentci/example/Cargo.toml
···00000000
···1+[package]
2+name = "example"
3+version = "0.1.0"
4+edition = "2021"
5+6+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
7+8+[dependencies]
···1+export * from "./src/dagger/index.ts";
2+export * as queries from "./src/dagger/queries.ts";
3+export { schema } from "./src/dagger/schema.ts";
+8
.fluentci/schema.graphql
···00000000
···1+### This file was generated by Nexus Schema
2+### Do not make changes to this file directly
3+4+5+type Query {
6+ build(src: String!): String
7+ test(src: String!): String
8+}
+39
.fluentci/src/aws/README.md
···000000000000000000000000000000000000000
···1+# AWS CodePipeline
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+The following command will generate a `buildspec.yml` file in your project:
9+10+```bash
11+fluentci ac init -t rust_pipeline
12+```
13+14+Generated file:
15+16+```yaml
17+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_aws_codepipeline
18+19+version: 0.2
20+phases:
21+ install:
22+ commands:
23+ - curl -fsSL https://deno.land/x/install/install.sh | sh
24+ - export DENO_INSTALL="$HOME/.deno"
25+ - export PATH="$DENO_INSTALL/bin:$PATH"
26+ - deno install -A -r https://cli.fluentci.io -n fluentci
27+ - curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
28+ - mv bin/dagger /usr/local/bin
29+ - dagger version
30+ build:
31+ commands:
32+ - fluentci run rust_pipeline test build
33+ post_build:
34+ commands:
35+ - echo Build completed on `date`
36+37+```
38+39+Feel free to edit the template generator at `.fluentci/src/aws/config.ts` to your needs.
···1+# Github Actions
2+3+[](https://pkg.fluentci.io/rust_pipeline)
4+[](https://deno.land/x/rust_pipeline)
5+
6+[](https://codecov.io/gh/fluent-ci-templates/rust-pipeline)
7+8+The following command will generate a `.github/workflows/tests.yml` file in your project:
9+10+```bash
11+fluentci gh init -t rust_pipeline
12+```
13+14+Or, if you already have a `.fluentci` folder (generated from `fluentci init -t rust`) in your project:
15+16+```bash
17+fluentci gh init
18+```
19+20+Generated file:
21+22+```yaml
23+# Do not edit this file directly. It is generated by https://deno.land/x/fluent_github_actions
24+25+name: Test
26+on:
27+ push:
28+ branches:
29+ - main
30+jobs:
31+ test:
32+ runs-on: ubuntu-latest
33+ steps:
34+ - uses: actions/checkout@v2
35+ - uses: denoland/setup-deno@v1
36+ with:
37+ deno-version: v1.37
38+ - name: Setup Fluent CI CLI
39+ run: deno install -A -r https://cli.fluentci.io -n fluentci
40+ - name: Setup Dagger
41+ run: |
42+ curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=0.8.1 sh
43+ sudo mv bin/dagger /usr/local/bin
44+ dagger version
45+ - name: Run Tests and Build
46+ run: fluentci run rust_pipeline test build
47+48+```
49+50+Feel free to edit the template generator at `.fluentci/src/github/config.ts` to your needs.