Message-ID: <gh-pgjdbc-pgjdbc-3124-c2022698719@github.com>
From: "sehrope (@sehrope)" <noreply+sehrope@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 27 Mar 2024 12:54:10 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3124: Add Windows and MacOS native certificate support
In-Reply-To: <gh-pgjdbc-pgjdbc-3124@github.com>
References: <gh-pgjdbc-pgjdbc-3124@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: sehrope
X-GitHub-Comment-Id: 2022698719
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3124
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3124#issuecomment-2022698719
Content-Type: text/plain; charset=utf-8

@minfrin You can enable actions to run on your pgjdbc fork as well. This is particularly useful if you want to try running something in CI without opening a PR in this repo. The GitHub Actions should work with no issues on your fork. The Windows / AppVeyor stuff is a bit finicky but in theory should work if you set up an account there as well.

(Note that I'm not suggesting opening this PR and running the CI on pgjdbc/pgjdbc was a bad idea ... I'm just suggesting an alternative for the future if you're trying out something else)