Skip to content

feat: defaulting env_token_name to None#77

Merged
MarcoMuellner merged 1 commit intomainfrom
68-env-token-name-flag-is-defaulted-to-access_token-its-not-possible-to-set-it-to-none-which-would-activate-different-jinja-template-features
Nov 28, 2024
Merged

feat: defaulting env_token_name to None#77
MarcoMuellner merged 1 commit intomainfrom
68-env-token-name-flag-is-defaulted-to-access_token-its-not-possible-to-set-it-to-none-which-would-activate-different-jinja-template-features

Conversation

@MarcoMuellner
Copy link
Owner

No description provided.

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.

--env-token-name flag is defaulted to access_token, its not possible to set it to none which would activate different jinja template features

1 participant