Skip to content

goose repository migration tasks #6135

@jamadeo

Description

@jamadeo

context: AAIF

The goose repo will move to a new home, and we'll need to tie up several loose ends to complete this beyond just moving the repo.

Code signing

Block currently signs goose releases using credentials from Apple / Microsoft. We'll need to determine which authority will sign future goose releases and how that should work.

Auto-updater

The auto updater is currently hard-coded to block/goose. We can improve this immediately.

Documentation page

The documentation page is hosted with GitHub pages, so there shouldn't be too much more to do there. But there is an integration with Inkeep that should use updated credentials.

Find/replace

We'll do a find-replace for block/goose, but we do need to be careful with certain instances. For example, this should not change (yet) because it is part of the config file path on some systems:

top_level_domain: "Block".to_string(),

Sub-issues

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestp1Priority 1 - High (supports roadmap)

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions