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: update maintainer key data #568

Merged
merged 3 commits into from
Mar 25, 2024

Conversation

williamcroberts
Copy link
Member

  • fix docs build
  • fix whitespace
  • add maintainer key details

Fixes: #566

Fixes sphinx build error:
/home/billdev/workspace/tpm2-pytss/docs/SECURITY.md:document isn't included in any toctree

Signed-off-by: Bill Roberts <bill.c.roberts@gmail.com>
Signed-off-by: Bill Roberts <bill.c.roberts@gmail.com>
Signed-off-by: Bill Roberts <bill.c.roberts@gmail.com>
Copy link

codecov bot commented Mar 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.47%. Comparing base (70a4ccc) to head (d4df77f).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #568   +/-   ##
=======================================
  Coverage   91.47%   91.47%           
=======================================
  Files          17       17           
  Lines        7014     7014           
  Branches     1010     1010           
=======================================
  Hits         6416     6416           
  Misses        426      426           
  Partials      172      172           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@whooo whooo merged commit 19aee3f into tpm2-software:master Mar 25, 2024
38 checks passed
@Foxboron
Copy link

The rebase merge removed the signatures from master.

@whooo
Copy link
Contributor

whooo commented Mar 26, 2024

The rebase merge removed the signatures from master.

Can't the commit from this branch used for you to establish trust?

@Foxboron
Copy link

Can't the commit from this branch used for you to establish trust?

In this case it's fine, the signed commit matches the unsigned one and I know this.

However unsigned commits are not worth anything when we are dealing with a chain of trust. We are using them to impute trust.

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.

releases > 2.1.0 are not done using signed tags
3 participants