Skip to content
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.

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

Feature Request: Optional target_url #159

Open
rfpludwick opened this issue Nov 28, 2024 · 6 comments · May be fixed by #160
Open

Feature Request: Optional target_url #159

rfpludwick opened this issue Nov 28, 2024 · 6 comments · May be fixed by #160

Comments

@rfpludwick
Copy link

rfpludwick commented Nov 28, 2024

I would love to be able to optionally set the target_url when setting the GH status. One of the Concourse CI systems I run is entirely private, but it does run pipelines for a public repository on GitHub. I'd like to be able to report build status, but without the URL as that is private information. Could define the optional target URL either in the resource configuration or on the put.

    on_success:
      put: gh-status
      inputs: [the-repo]
      params: {state: success, target_url: false}

---

- name: gh-status
  type: cogito
  check_every: never
  source:
    owner: ((github-owner))
    repo: ((your-repo-name))
    access_token: ((github-PAT))
    target_url: false
@rfpludwick rfpludwick changed the title Feat: Optional target_url Feature Request: Optional target_url Nov 28, 2024
@marco-m-pix4d
Copy link
Contributor

Ah, I understand the reasoning. Makes sense. I appreciate that you proposed a possible and backwards compatible configuration for this.

My first reaction is wondering if there is a way to make the intent more explicit. For example: omit_target_url (bool). In any case, this is a nitpick.

@rfpludwick
Copy link
Author

rfpludwick commented Nov 29, 2024

@marco-m-pix4d Yeah, something like omit_target_url is probably better! I like that.

@marco-m-pix4d
Copy link
Contributor

@rfpludwick I discussed with the team and we think it is a reasonable request. Would you be interested in proposing a PR?

@rfpludwick
Copy link
Author

@marco-m-pix4d I can give it a try. My Go experience isn't super deep, but I think I can muddle my way through to an acceptable PR eventually.

marco-m-pix4d added a commit that referenced this issue Dec 6, 2024
@marco-m-pix4d marco-m-pix4d linked a pull request Dec 6, 2024 that will close this issue
@marco-m-pix4d
Copy link
Contributor

I had some time and went ahead with #160.

marco-m-pix4d added a commit that referenced this issue Dec 6, 2024
@rfpludwick
Copy link
Author

Ah fantastic! Thanks @marco-m-pix4d!

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 a pull request may close this issue.

2 participants