Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: set up guide #155

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: set up guide #155

wants to merge 2 commits into from

Conversation

camshaft
Copy link
Member

@camshaft camshaft commented Jan 16, 2025

Description of changes:

This change sets up a guide to describe some of the concepts in duvet and how to configure the workflow. While it's not exhaustive, it's a lot better than what we have no, which is nothing.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@camshaft camshaft deployed to github-pages January 16, 2025 07:53 — with GitHub Actions Active
@camshaft camshaft marked this pull request as ready for review January 16, 2025 07:59
@camshaft camshaft requested a review from a team as a code owner January 16, 2025 07:59
@camshaft camshaft force-pushed the camshaft/guide branch 3 times, most recently from d5d0e60 to cca2e7a Compare January 16, 2025 08:24
In a strongly-typed language, this requirement is being both implemented and tested by the compiler.

```rust
//= my-spec.md#section
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this have //= type=implication?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! good catch :)

Implementations MAY panic on invalid arguments.
```

In our example here, we've chosen _not_ to panic, but instead return an error. Annotations with the `exception` type are expected to provide a reason as to why the requirement is not being implemented.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Annotations with the exception type are expected

I forget if "reason" is required for this, maybe make it clear one way or the other if its optional or required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants