Skip to content

Fix: astropy landing should use labels vs partners - #576

Merged
lwasser merged 1 commit into
pyOpenSci:mainfrom
lwasser:astro2
Mar 4, 2025
Merged

lwasser merged 1 commit into
pyOpenSci:mainfrom
lwasser:astro2

Conversation

@lwasser

@lwasser lwasser commented Mar 3, 2025

Copy link
Copy Markdown
Member

closes #575

This is just a tiny fix to make sure we're grabbing affiliated data from an editor curated field

@lwasser lwasser changed the title Fix: astropy landing shoould use labels vs partners Fix: astropy landing should use labels vs partners Mar 4, 2025
@pllim

pllim commented Mar 4, 2025

Copy link
Copy Markdown
Contributor

@lwasser

lwasser commented Mar 4, 2025

Copy link
Copy Markdown
Member Author

@pllim yes - it's a circle CI think i figured out how to fix it - you have to force relative paths. the working path is this:

https://output.circle-artifacts.com/output/job/5646506d-b78e-4155-a44d-dd3788affb54/artifacts/0/_site/communities/astropy.html

it's a quirk that is specific to circleCI / CI rendering outputs where you have to tell jekyll to create the path. I haven't gone through the entire site to fix it yet :( but it's only a ci issue the live site will be fine.

@lwasser
lwasser merged commit 05b0e63 into pyOpenSci:main Mar 4, 2025
@lwasser
lwasser deleted the astro2 branch March 4, 2025 17:01
lwasser added a commit to lwasser/pyopensci.github.io that referenced this pull request Jun 9, 2026
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 this pull request may close these issues.

Astropy page: let's use labels as a source of truth for astropy-affiliated packages. (rather than the partners field)

2 participants