Initial commit.

Author: da-tanabe

.circleci/config.yml

@@ -0,0 +1,30 @@
+version: 2.1
+setup: true
+orbs:
+  orb-tools: circleci/orb-tools@12.2.0
+  shellcheck: circleci/shellcheck@3.2.0
+filters: &filters
+  tags:
+    only: /.*/
+workflows:
+  lint-pack:
+    jobs:
+      - orb-tools/lint:
+          filters: *filters
+      - orb-tools/pack:
+          filters: *filters
+          pre-steps:
+            - run:
+                name: Write orb version file
+                command: echo "${CIRCLE_SHA1}" | tee /home/circleci/orb-version
+      - orb-tools/review:
+          filters: *filters
+      - shellcheck/check:
+          filters: *filters
+      # Triggers the next workflow in the Orb Development Kit.
+      - orb-tools/continue:
+          pipeline_number: << pipeline.number >>
+          vcs_type: << pipeline.project.type >>
+          orb_name: <orb-name>
+          requires: [orb-tools/lint, orb-tools/pack, orb-tools/review, shellcheck/check]
+          filters: *filters

.circleci/test-deploy.yml

@@ -0,0 +1,69 @@
+version: 2.1
+orbs:
+  # Your orb will be automatically injected here during the pipeline.
+  # Reference your orb's jobs and commands below as they will exist when built.
+  orb-tools: circleci/orb-tools@12.2.0
+  # The orb definition is intentionally not included here. It will be injected into the pipeline.
+  <orb-name>: {}
+# Use this tag to ensure test jobs always run,
+# even though the downstream publish job will only run on release tags.
+filters: &filters
+  tags:
+    only: /.*/
+# Filter for release tags.
+release-filters: &release-filters
+  branches:
+    ignore: /.*/
+  tags:
+    only: /^v[0-9]+\.[0-9]+\.[0-9]+$/
+jobs:
+  # Create jobs to test the commands of your orbs.
+  # You may want to add additional validation steps to ensure the commands are working as expected.
+  command-test:
+    docker:
+      - image: cimg/base:current
+    steps:
+      - checkout
+      # Run your orb's commands to validate them.
+      - <orb-name>/nix
+      # Formatting checks. They depend on nix itself, so we have to run formatting checks of
+      # our own orb while we test the orb itself.
+      - run:
+          name: Run formatting
+          command: treefmt --ci
+      # Test nix environment
+      - run:
+          name: Test nix environment
+          command: test/test-nix-environment.sh
+workflows:
+  test-deploy:
+    jobs:
+      # Make sure to include "filters: *filters" in every test job you want to run as part of your deployment.
+      # Test your orb's commands in a custom job and test your orb's jobs directly as a part of this workflow.
+      - command-test:
+          name: first run
+          filters: *filters
+          context: artifactory
+      - command-test:
+          name: second run
+          requires:
+            - first run
+          filters: *filters
+          context: artifactory
+      # The orb must be re-packed for publishing, and saved to the workspace.
+      - orb-tools/pack:
+          filters: *release-filters
+          pre-steps:
+            - run:
+                name: Write orb version file
+                command: echo "${CIRCLE_SHA1}" | tee /home/circleci/orb-version
+      - orb-tools/publish:
+          orb_name: digital-asset/build
+          vcs_type: << pipeline.project.type >>
+          pub_type: production
+          # Ensure this job requires all test jobs and the pack job.
+          requires:
+            - orb-tools/pack
+            - second run
+          context: circleci-orb-publish
+          filters: *release-filters

.envrc

@@ -0,0 +1,5 @@
+# -*- bash -*-
+# shellcheck shell=bash
+
+watch_dir nix
+use flake

.gitignore

@@ -0,0 +1,4 @@
+# orb.yml is "packed" from source, and not published directly from the repository.
+orb.yml
+.DS_Store
+.direnv

.treefmt.toml

@@ -0,0 +1,24 @@
+excludes = ["COPYRIGHT", "LICENSE"]
+
+[formatter.mdformat]
+command = "mdformat"
+excludes = []
+includes = ["*.md"]
+options = []
+
+[formatter.nixfmt-rfc-style]
+command = "nixfmt"
+excludes = []
+includes = ["*.nix"]
+options = []
+
+[formatter.shfmt]
+command = "shfmt"
+options = ["-i", "2", "-s", "-w"]
+includes = ["*.sh"]
+
+[formatter.yamlfmt]
+command = "yamlfmt"
+excludes = []
+includes = ["*.yaml", "*.yml"]
+options = []

.yamllint

@@ -0,0 +1,7 @@
+extends: relaxed
+
+rules:
+    line-length:
+        max: 200
+        allow-non-breakable-inline-mappings: true
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [community@digitalasset.com](mailto:community@digitalasset.com). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,71 @@
+# Contributing to nix-orb
+
+Welcome! This document provides a high-level overview of how to contribute to the development of nix-orb.
+
+(For information on how to build, test, and work on the codebase, see the [README](./README.md).)
+
+There are many ways you can contribute beyond coding. For example, you can report problems, report and clarify issues, and write documentation. If you're completely new to open source, the [Open Source Guides](https://opensource.guide) is a great place to start.
+
+## Code of conduct
+
+This project and everyone participating in it is governed by the [Daml Code of Conduct](./CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [community@digitalasset.com](mailto:community@digitalasset.com).
+
+## Git conventions
+
+For Git commit messages, our principle is that `git log --pretty=oneline` should give readers a clear idea of what has changed and the detailed descriptions should help them understand the rationale. To achieve this:
+
+- Commits must have a concise, imperative title, prefixed with either `python` or `meta` e.g.:
+  - *meta: Add legalese (CONTRIBUTING notice, LICENSE, notice).*
+  - *python: Improve explanation of …*
+  - *python: Remove module X because it is not used.*
+- Commits should have a description that concisely explains the rationale and context for the change if that is not obvious.
+- Commit descriptions should include a `Fixes #XX` line indicating what GitHub issue number the commit fixes.
+- The git logs are not intended for user-facing change logs, but should be a useful reference when writing them.
+
+## Pull request checklist
+
+- Read this document (contribution guidelines).
+- Does your PR include appropriate tests?
+- Make sure your PR title and description makes it easy for other developers to understand what the contained commits do.
+- If your PR corresponds to an issue, add “Fixes #XX” to your pull request description. This will auto-close the corresponding issue when the commit is merged into master and tie the PR to the issue.
+- If your PR includes user-facing changes, you must add a line describing the change to the [release notes](docs/source/support/release-notes.rst) as part of your PR.
+
+## Working with issues
+
+We use issues and [pull requests](https://help.github.com/articles/about-pull-requests/) to collaborate and track our work. Anyone is welcome to open an issue. If you just want to ask a question, please ask away on [Stack Overflow](https://stackoverflow.com/questions/tagged/daml) using the tag `daml`.
+
+We encourage everyone to vote on issues that they support or not:
+
+- 👍 - upvote
+- 👎 - downvote
+
+When you start working on an issue, we encourage you to tell others about it in an issue comment. If other contributors know that this issue is already being worked on, they might decide to tackle another issue instead.
+
+When you add `TODO` (nice to have) and `FIXME` (should fix) comments in the code, we encourage you to create a corresponding issue and reference it as follows:
+
+- `TODO(#XX): <description>` where `#XX` corresponds to the GitHub issue.
+- `FIXME(#XX): <description>` where `#XX` corresponds to the GitHub issue.
+
+### Labels
+
+We use labels to indicate what component the issue relates to (`component/...`). We use some special labels:
+
+- `broken` to indicate that something in the repo is seriously broken and needs to be fixed.
+- `discussion` to indicate the issue is to discuss and decide on something.
+- `good-first-issue` to indicate that the issue is suitable for those who want to contribute but don't know where to start.
+
+By default, issues represent "work to be done" -- that might be features, improvements, non-critical bug fixes, and so on.
+
+### Milestones
+
+Issues are grouped into *milestones* that correspond to future planned releases of the library. Issues without a milestone are treated as in need of triaging.
+
+The active milestones arse listed [here](https://github.com/DACH-NY/nix-orb/milestones).
+
+## Discussions
+
+Discussions on this repository should be limited to the nix-orb library.
+
+# Thank you!
+
+Thank you for taking the time to contribute!

COPYRIGHT

@@ -0,0 +1,2 @@
+Copyright (c) 2025 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
+SPDX-License-Identifier: Apache-2.0