Skip to content

Update references to the repo to reflect move to Grokability org #16701

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 12 commits into from
Apr 15, 2025
Merged

Update references to the repo to reflect move to Grokability org #16701

merged 12 commits into from
Apr 15, 2025

Conversation

@jerm
Copy link
Member

@jerm jerm commented Apr 14, 2025 •
edited by snipe
Loading

Some of this is cosmetic -- the github redirect will make things Just
Work -- though we still want it to be correct.

Some things are necessary -- like "which repo is this?" in github
actions that decide to do builds or not.

A simple find/replace would overreach, because some things like
dockerhub will still be snipe/snipe-it, so this was done more manually.
Hopefully it got everything

Jeremy Price added 10 commits April 3, 2025 11:36
@jerm jerm requested review from snipe and uberbrady as code owners April 14, 2025 19:37
@what-the-diff
Copy link

what-the-diff bot commented Apr 14, 2025

PR Summary

  • Update Repository References
    The references in workflow files, configuration files, and documentation were updated from snipe/snipe-it to grokability/snipe-it.
  • Change GitHub Actions Logic
    The logic of our GitHub actions was changed to ensure jobs are only ran for our recently updated repository - grokability/snipe-it.
  • Modify Dockerfile References
    The code used by Docker for creating our software's environment has been modified to fetch its information from the new repository URL.
  • Adjust Installation Script
    Our software's installation process has been adjusted to get snipeit.sh (an important script file) directly from grokability/snipe-it.
  • Update Maintainer Label
    We updated the maintainer label in the Dockerfile to reflect the new organization.
  • Change Documentation Links
    References in the written instructions and information have been changed to point to our new grokability/snipe-it repository.
  • Update Comments in Code
    Comments in various code files have been updated to reference our new repository links.
  • Update Environment Variables and URLs
    Updates have been made to the environment variables and URLs in many scripts and source files to reflect the migration to the grokability/snipe-it repository.

@snipe
Copy link
Member

snipe commented Apr 14, 2025

@jerm do we need to wait to merge this until immediately after the switchover?

Jeremy Price and others added 2 commits April 14, 2025 12:55
Separate docker builds into Intel/ARM builds
545e074 
Now that we're moving to a paid org, we have native ARM github action
runners available, which means we can streamline our ARM-based docker
image builds by not having them run emulated.

I've switched our worker split from ubuntu/alpine to Intel/ARM...  if we
hate this we can make it 4 separate workflows, but i don't see an issue
with this one.
@snipe
Merge pull request #16702 from snipe/separate-docker-architecture-builds
42e1987 
Separate docker builds into Intel/ARM builds
@snipe snipe merged commit 71d8f1e into develop Apr 15, 2025
9 of 11 checks passed
@snipe snipe deleted the repo-move branch April 15, 2025 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@uberbrady uberbrady Awaiting requested review from uberbrady uberbrady is a code owner

@snipe snipe Awaiting requested review from snipe snipe is a code owner

Assignees

No one assigned

Labels

backend config css custom fields dependencies Pull requests that update a dependency file docker frontend skins tests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jerm @snipe