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: document Azure Trusted Signing workflow #210

Open
wants to merge 3 commits into
base: v6
Choose a base branch
from

Conversation

nikwen
Copy link

@nikwen nikwen commented Nov 29, 2024

@nikwen
Copy link
Author

nikwen commented Nov 29, 2024

If someone is motivated, they could add a more straightforward API to Electron Forge for Trusted Signing.

@nikwen nikwen force-pushed the docs-azure-trusted-signing branch from e75e748 to 84f0ae0 Compare November 29, 2024 23:25
@nikwen
Copy link
Author

nikwen commented Nov 29, 2024

There'll be one more linter issue MD024/no-duplicate-heading. I'll fix that soon.

@nikwen
Copy link
Author

nikwen commented Dec 3, 2024

I expected no-duplicate-heading to fail, but the Electron project disables it. Thus, linting worked.

Still, to generate distinct anchors for all headings, I set two anchor IDs manually.

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.

Implement Azure Trusted signing
2 participants