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

πŸ‘· (doc) [NO-ISSUE]: Sync doc with ledgerhq/developer-portal #598

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

valpinkman
Copy link
Member

πŸ“ Description

Adds a new workflow to sync our documentation to the developer-portal when merging to main

❓ Context

  • JIRA or GitHub link: [NO-ISSUE]
  • Feature:

βœ… Checklist

Pull Requests must pass CI checks and undergo code review. Set the PR as Draft if it is not yet ready for review.

  • Covered by automatic tests
  • Changeset is provided
  • Impact of the changes:
    • list of the changes

🧐 Checklist for the PR Reviewers

  • The code aligns with the requirements described in the linked JIRA or GitHub issue.
  • The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
  • There are no undocumented trade-offs, technical debt, or maintainability issues.
  • The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
  • Any new dependencies have been justified and documented.

Copy link

vercel bot commented Jan 10, 2025

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
device-sdk-ts-sample βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Jan 16, 2025 3:18pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
doc-device-management-kit ⬜️ Ignored (Inspect) Visit Preview Jan 16, 2025 3:18pm

Copy link
Contributor

github-actions bot commented Jan 10, 2025

Messages
⚠️ No changeset file found in the PR. Please add a changeset file.

Generated by 🚫 dangerJS against a41da56

@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 1f8296b to 6b167db Compare January 10, 2025 16:37
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 6b167db to acb66cd Compare January 13, 2025 09:28
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from acb66cd to 6662f06 Compare January 15, 2025 08:44
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 6662f06 to b508341 Compare January 15, 2025 10:12
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from b508341 to 291dc31 Compare January 15, 2025 11:11
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 291dc31 to 8c45b98 Compare January 15, 2025 11:12
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch 2 times, most recently from e817966 to 6dee66d Compare January 16, 2025 10:30
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 6dee66d to 83d3da5 Compare January 16, 2025 14:38
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 83d3da5 to 4e57819 Compare January 16, 2025 14:43
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 4e57819 to 20599b7 Compare January 16, 2025 14:48
@valpinkman valpinkman force-pushed the chore/no-issue-sync-doc-to-portal branch from 20599b7 to a41da56 Compare January 16, 2025 15:17
@valpinkman valpinkman marked this pull request as ready for review January 16, 2025 15:17
@valpinkman valpinkman requested a review from a team as a code owner January 16, 2025 15:17
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.

1 participant