FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

feat: set `remote.type` dynamically from env · Issue #1099 · python-semantic-release/python-semantic-release · GitHub

Repository navigation

feat: set remote.type dynamically from env #1099

Description

Feature Request

Description

I have a template project hosted both on GitHub and GitLab mostly for demostration, and I want to leverage both GitHub Actions and GitLab CI/CD, so I need to set the remote.type dynamically. But it seems that a validation error will happen when I try to set an env for it.

Expected behavior

Possibility to set remote.type with env.

Actual behavior

A validation error is raised.

Environment

  • Operating System (w/ version): Ubuntu 22.04
  • Python version: 3.10.12
  • Pip version: N/A
  • Semantic-release version: 9.14.0
  • Build tool (w/ version): N/A
pip freeze
N/A

git log --oneline --decorate --graph --all -n 50
N/A

Configuration

Semantic Release Configuration
[tool.semantic_release.remote.type]
env = "SEMANTIC_RELEASE_REMOTE_TYPE"
default = "github"

Build System Configuration
N/A

GitHub Actions Job Definition
N/A

Execution Log

semantic-release -vv command
[06:05:45] DEBUG    [main.main] logging level set to: DEBUG                                                                                                                                             main.py:124
🛡 You are running in no-operation mode, because the '--noop' flag was supplied
           DEBUG    [main.main] global cli options: GlobalCommandLineOptions(noop=True, verbosity=2, config_file='pyproject.toml', strict=False)                                                        main.py:139
           INFO     [util.load_raw_config_file] Loading configuration from pyproject.toml                                                                                                                util.py:79
           DEBUG    [util.load_raw_config_file] Trying to parse configuration pyproject.toml in TOML format                                                                                              util.py:82
1 validation error for RawConfig
remote.type
  Input should be 'bitbucket', 'github', 'gitlab' or 'gitea' [type=enum, input_value={'env': 'SEMANTIC_RELEASE...E', 'default': 'github'}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.9/v/enum

Additional context

N/A

Activity

  1. added
    bugSomething isn't working properly
    triagewaiting for initial maintainer review
    on Nov 16, 2024
  2. added
    featureA new feature or a feature request
    confirmedPrevent from becoming stale
    and removed
    bugSomething isn't working properly
    triagewaiting for initial maintainer review
    on Nov 16, 2024
  3. codejedi365 commented on Nov 16, 2024

    Contributor

    @huxuan, unfortunately it's not a bug, but it is not configured to support an env variable input at this time.

    Changing this to a feature request and adding it to the backlog. Thanks for the desired use case. This may ultimately help out #149.

  4. changed the title [-]Validation error when trying to set `remote.type` dynamically with env.[/-] [+]Request setting `remote.type` dynamically from env[/+] on Nov 16, 2024
  5. huxuan commented on Nov 16, 2024

    Author

    Sorry I tried to search but did not find that issue, will close this one as already tracked there. Thanks for the prompt response!

  6. codejedi365 commented on Nov 16, 2024

    Contributor

    That's not quite what I meant, I just realized that the resolution of this issue would partially lead to a resolution of the other one. The other one has been open for years without really any solution that made sense, is all.

  7. changed the title [-]Request setting `remote.type` dynamically from env[/-] [+]feat: set `remote.type` dynamically from env[/+] on Nov 18, 2024
  8. github-actions commented on Jan 18, 2025

    It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

  9. 1 remaining item

  10. github-actions commented on Mar 20, 2025

    It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

  11. codejedi365 commented on Mar 21, 2025

    Contributor

    Still in backlog

  12. github-actions commented on May 21, 2025

    It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

  13. codejedi365 commented on May 21, 2025

    Contributor

    Still in backlog

  14. github-actions commented on Aug 20, 2025

    It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

  15. codejedi365 commented on Aug 31, 2025

    Contributor

    No update yet, still in backlog.

  16. github-actions commented on Nov 29, 2025

    It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmedPrevent from becoming stalefeatureA new feature or a feature requestneeds-updateNeeds status update from maintainers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL