Skip to content

OSOE-1156: Mention the Open Pull Request workflow in the docs #99

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.

Sign up for GitHub

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

Merged
BenedekFarkas merged 2 commits into from
Feb 17, 2026
Merged

OSOE-1156: Mention the Open Pull Request workflow in the docs #99

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46d66c6
Mention the Open Pull Request workflow in the docs
Piedone Feb 16, 2026
000bd66
Typo
Piedone Feb 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Fork the [DotNest Core SDK](https://github.com/Lombiq/DotNest-Core-SDK) reposito
DESTINATION_TOKEN: ${{ secrets.AWESOME_PROJECT_MIRROR_TOKEN }}
```

In case new commits are pushed to your fork from the SDK, check the changes (e.g. new modules might be added that you also need to add to your custom solution) and merge `dev` into your development branch.
In case new commits are pushed to your fork from the SDK, check the changes (e.g. new modules might be added that you also need to add to your custom solution) and merge `dev` into your development branch. You can also automate this with the [Open Pull Request workflow](https://github.com/Lombiq/GitHub-Actions/blob/dev/Docs/Workflows/Productivity/OpenPullRequest.md).

## Theme development

Expand Down
Loading