Repository navigation
Add option to connect to OEP with token - #889
Merged
Merged
Conversation
lenzim97
previously approved these changes
Oct 16, 2026
lenzim97
left a comment
lenzim97
left a comment
Contributor
There was a problem hiding this comment.
Both options to connect via Token work for me
lenzim97
reviewed
Oct 16, 2026
lenzim97
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #884
This branch add the option to connect to the OEP with a personal token.
The token has to be either stored in the env variables or
/home/USER/.etrago_database/OEP_TOKEN.txt.I quickly tried it out and it seems to work fine.
Could you maybe check it again @lenzim97?