Skip to content
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

chore: updates after repo moved orgs #434

Closed
wants to merge 2 commits into from
Closed

chore: updates after repo moved orgs #434

wants to merge 2 commits into from

Conversation

richardcase
Copy link
Member

What this PR does / why we need it:

Changes after the repo was moved from the Weaveworks GitHub org to the
Weaveworks-liquidmetal GitHub org. Most of the changes are Go module
imports/definitions. There where a small numbre of lint issues after
moving and these have been fixed as well.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes

Changes after the repo was moved from the `Weaveworks` GitHub org to the
`Weaveworks-liquidmetal` GitHub org. Most of the changes are Go module
imports/definitions. There where a small numbre of lint issues after
moving and these have been fixed as well.

Signed-off-by: Richard Case <richard@weave.works>
@richardcase richardcase added the kind/refactor Only refactoring changes label May 9, 2022
@yitsushi
Copy link
Contributor

yitsushi commented May 9, 2022

yitsushi/devmapper-containerd-action@v1.0.1 is not allowed to be used in weaveworks-liquidmetal/flintlock. Actions in this workflow must be: within a repository that belongs to your Enterprise account or created by GitHub.

That's strange. Should we move over that repo to weaveworks?

I have no idea who can answer this, maybe @morancj ?

@richardcase
Copy link
Member Author

That's strange. Should we move over that repo to weaveworks?

I have no idea who can answer this, maybe @morancj ?

@yitsushi - i have updated the org settings to allow your GHA. So it should work now.

@richardcase
Copy link
Member Author

Closing to kick off the GH actions again

@morancj
Copy link

morancj commented May 10, 2022

Thanks Richard for allowing specific actions and not just enabling all globally. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/refactor Only refactoring changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants