Skip to content

We've moved from snipe/snipe-it to grokability/snipe-it! #16697

@snipe

Description

@snipe

Important

You should not have to do anything to continue using and upgrading Snipe-IT. Github's redirects should handle everything for you.

Image

Don't worry - this won't affect you much (if at all), we're just letting you know in case you have any bespoke integrations, or in case you get freaked out that the namespace has changed.

Why the move?

Moving the repo to the @grokability namespace will let us handle team member roles with a bit more nuance and granularity, and expose some of the Github organization features we're already paying for.

Additionally, it's just more consistent, since @grokability is the company that makes and maintains Snipe-IT, and all of the associated integrations and helper scripts live within that organization's namespace.

How does this affect licenses, support, etc?

The license isn't changing, pricing and urls for those that choose to host with us or get support with us isn't changing, staffing isn't changing, nothing at all else changes, just where to find it.

How does this affect open PRs, issues, and discussions?

All issues, PRs, etc will be transferred over automatically, and web links should automatically redirect as well.

The target date for this is tomorrow, April 15, 2025, but again, no action should be required by you. It should Just Work™.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions