Skip to content

Clarify docs with required/optional configuration #665

Description

@bernardcooke53

Please describe your problem. Include links to any relevant pages or files.

From #659:

What was difficult to me was a) reading the python-semantic-release documentation, it seems inclomplete, particularly regarding the Gitlab configuration and b) identifying deprecated configuration variables. For instance, hvcs, hvcs_domain, and hvcs_api_domain are not mentioned anymore in latest/configuration, but can be found via search (documentation) somewhere nested in the code. They still seem to work and required to get a custom Gitlab CI working. Also, in the migrating_from_v7, it is not mentioned that the env variable GL_TOKEN, which formerly apparently identified Gitlab-CI, does not work anymore and it is required to explicitly add:

[tool.semantic_release.remote]
name = "origin"
type = "gitlab"
  • Ensure options are documented properly
  • Add required/optional indicator to configuration options (put required at top of page, easier to find)
  • Review & clarify v7 vs v8 config in migration guide

Activity

  1. added
    confirmedPrevent from becoming stale
    and removed on Mar 29, 2024
  2. github-actions commented on May 28, 2024

    @github-actions

    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?

  3. codejedi365 commented on May 28, 2024

    @codejedi365
    Contributor

    Still in the backlog, however, the configuration docs have improved significantly and now document the missing remote options. Optional vs required is not annotated but I'm not sure this actually exists as we use defaults for everything.

    Automatically determining which CI env sounds intriguing but not there yet for that.

  4. github-actions commented on Jul 29, 2024

    @github-actions

    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?

  5. codejedi365 commented on Jul 29, 2024

    @codejedi365
    Contributor

    No change, still in backlog.

  6. 6 remaining items

  7. codejedi365 commented on Dec 2, 2024

    @codejedi365
    Contributor

    Still in backlog

  8. github-actions commented on Feb 2, 2025

    @github-actions

    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. codejedi365 commented on Feb 2, 2025

    @codejedi365
    Contributor

    Still in backlog

  10. github-actions commented on Apr 4, 2025

    @github-actions

    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 Apr 4, 2025

    @codejedi365
    Contributor

    Still in backlog

  12. github-actions commented on Jun 4, 2025

    @github-actions

    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 Jun 14, 2025

    @codejedi365
    Contributor

    Resolved significantly with last release. GitLab docs has its own 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

    docsImprovements or additions to documentationneeds-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