Skip to content

Commit

Permalink
first
Browse files Browse the repository at this point in the history
  • Loading branch information
pldubouilh committed Jul 31, 2023
1 parent 77b81d2 commit 5de2292
Show file tree
Hide file tree
Showing 36 changed files with 2,691 additions and 1 deletion.
2 changes: 2 additions & 0 deletions .dockerignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
./target
/build
13 changes: 13 additions & 0 deletions .github/workflows/always.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
name: ci
on: [push]
jobs:
build:
name: Build
runs-on: ubuntu-latest
steps:
- name: dependencies
uses: actions/checkout@v3

- name: run
run: make ci

39 changes: 39 additions & 0 deletions .github/workflows/prerelease.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
name: prerelease
on:
push:
branches:
- 'main'
jobs:
release:
name: 'Build'
runs-on: ubuntu-latest
steps:
- name: checkout
uses: actions/checkout@v3

- name: 'Install dependencies'
run: |
sudo apt -y update
sudo apt -y install musl-tools clang
rustup target add x86_64-unknown-linux-musl
- name: 'Build artifacts'
run: make release

- name: 'Upload thistle-yocto-build'
uses: svenstaro/upload-release-action@v2
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: dist/thistle-yocto-build-x86_64-unknown-linux-musl
asset_name: thistle-yocto-build
tag: edge
overwrite: true

- name: 'Upload sha256sums.txt'
uses: svenstaro/upload-release-action@v2
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: dist/sha256sums.txt
asset_name: sha256sums.txt
tag: edge
overwrite: true
45 changes: 45 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: Release
on:
push:
tags: ["v[0-9]+.[0-9]+.[0-9]+*"]

jobs:
release:
name: Build
runs-on: ubuntu-latest
steps:
- name: checkout
uses: actions/checkout@v3

- name: dependencies
run: |
sudo apt -y update
sudo apt -y install musl-tools clang
rustup target add x86_64-unknown-linux-musl
- name: run
run: make release

- name: upload thistle-yocto-build
uses: svenstaro/upload-release-action@v2
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: dist/thistle-yocto-build-x86_64-unknown-linux-musl
asset_name: thistle-yocto-build
tag: ${{ github.ref }}
overwrite: true

- name: upload sha256sums.txt
uses: svenstaro/upload-release-action@v2
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: dist/sha256sums.txt
asset_name: sha256sums.txt
tag: ${{ github.ref }}
overwrite: true

- name: release-tag
run: |
set -euxo pipefail
echo "RELEASE_VERSION=${GITHUB_REF#refs/tags/v}" >> $GITHUB_ENV
7 changes: 7 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
/target
/target_ra
/layers
/build
/test
/dist
.thistlebuild.sh
4 changes: 4 additions & 0 deletions .rustfmt.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
fn_call_width=90
attr_fn_like_width=90
chain_width=90
max_width=110
24 changes: 24 additions & 0 deletions .vscode/launch.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "lldb",
"request": "launch",
"name": "thistle-yocto-build",
"cargo": {
"args": ["build"],
"filter": {
"name": "thistle-yocto-build",
"kind": "bin"
}
},
"args": ["build", "samples/qemuarm64.yml"],
"env": {
"DRYRUN": "1",
}
},
]
}
3 changes: 3 additions & 0 deletions CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@

# See https://help.github.com/articles/about-codeowners/
* @thistletech/engineering
132 changes: 132 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall
community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of
any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address,
without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders 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, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
<support@thistle.tech>.
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the
community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
18 changes: 18 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Contributing to Project

## Code of conduct

Thank you for considering contributing to the project. Please follow the [code
of conduct](./CODE_OF_CONDUCT.md) when conbributing.

## How to contribute

Pull requests are welcome. Please make an effort to follow existing code style
to maximize readability. Please make sure all test pass.

Bug reports and feature requests through "Issues" are welcome. Please include
reproducing steps in a bug report. Please provide a detailed description in a
feature request.

We require that all commits in this repository [be
signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
Loading

0 comments on commit 5de2292

Please sign in to comment.