-
Notifications
You must be signed in to change notification settings - Fork 0
Allow PRs against any branch in forks while restricting CI checks to main in astropy/astropy #5
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
Allow PRs against any branch in forks while restricting CI checks to main in astropy/astropy #5
Conversation
Cannot use the version setter because we allow v1.0 files to be read from XML even though we don't allow someone to create one with the APIs directly.
This ensures that error messages can report the actual version without having to work it out from the or_later values.
Without this change the COOSYS was coming before INFO and this
was failing linting because the schema requires INFO to come
first.
ERROR (l.8, c.59): cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.ivoa.net/xml/VOTable/v1.3":INFO}'.
One of '{"http://www.ivoa.net/xml/VOTable/v1.3":COOSYS,
"http://www.ivoa.net/xml/VOTable/v1.3":TIMESYS,
"http://www.ivoa.net/xml/VOTable/v1.3":GROUP,
"http://www.ivoa.net/xml/VOTable/v1.3":PARAM,
"http://www.ivoa.net/xml/VOTable/v1.3":LINK,
"http://www.ivoa.net/xml/VOTable/v1.3":TABLE,
"http://www.ivoa.net/xml/VOTable/v1.3":RESOURCE,
WC[##other:"http://www.ivoa.net/xml/VOTable/v1.3"]}' is expected.
…ng a `PyObject*` type
Fix bug in Wcs.wcs.print_contents() related to stdout buffer not bein…
FIX: Issue 15397
Fix _naxis dimensionality
…th more than 2 dimensions but with _naxis not set would fail, and that slicing a WCS with an ellipsis would not return a WCS object but a SlicedFITSWCS instead
|
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
|
@copilot also update the towncrier CI check to only apply to PRs on the astropy repo. |
Co-authored-by: nstarman <[email protected]>
…tory Co-authored-by: nstarman <[email protected]>
Updated the towncrier changelog check in |
|
@copilot also update the milestone check to only apply to PRs on the astropy repo, not forks. |
Co-authored-by: nstarman <[email protected]>
|
@copilot does |
…ub scripts Co-authored-by: nstarman <[email protected]>
You're absolutely right! The simple |
Allow controlling warnings when converting deprecated units to strings
Fixes CI workflows to only enforce branch, changelog, and milestone restrictions in the main
astropy/astropyrepository, allowing forks to open PRs against any branch without CI restrictions.Problem
The current CI checks in
.github/workflows/ci_workflows.yml,.github/workflows/check_changelog.yml, and.github/workflows/check_milestone.ymlapply to all repositories, including forks. This means that users working in their own forks cannot open PRs against development branches or feature branches - they are forced to only target the main branch and must include changelog entries and milestones, which limits development workflow flexibility in forks.Solution
Modified the base branch check, towncrier changelog check, and milestone check to only apply when the repository is the main
astropy/astropyrepository using the simpleif: github.repository == 'astropy/astropy'condition.For the main repository (
astropy/astropy):For fork repositories (e.g.,
user/astropy):Changes
Base Branch Check (
ci_workflows.yml):github.repository == 'astropy/astropy'condition to the existing checkTowncrier Changelog Check (
check_changelog.yml):if: github.repository == 'astropy/astropy'condition to the towncrier actionMilestone Check (
check_milestone.yml):if: github.repository == 'astropy/astropy'conditionThe changes are minimal and maintain backward compatibility while enabling the desired fork flexibility for branch targeting, changelog requirements, and milestone requirements. All implementations use the simple and clean
if: github.repository == 'astropy/astropy'pattern.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.