refactor: rename project to falcosecurity/pigeon

Signed-off-by: Jason Dellaluce <[email protected]>
falcosecurity · Feb 22, 2023 · b99b2bc · b99b2bc
1 parent b2fda30
commit b99b2bc
Show file tree

Hide file tree

Showing 6 changed files with 14 additions and 11 deletions.
diff --git a/README.md b/README.md
@@ -1,8 +1,8 @@
 # Pigeon
 
-[![Latest](https://img.shields.io/github/v/release/FedeDP/Pigeon)](https://github.com/FedeDP/Pigeon/releases/latest)
-[![Go Report Card](https://goreportcard.com/badge/github.com/FedeDP/Pigeon)](https://goreportcard.com/report/github.com/FedeDP/Pigeon)
-[![CI build](https://github.com/FedeDP/Pigeon/actions/workflows/ci.yaml/badge.svg)](https://github.com/FedeDP/Pigeon/actions/workflows/ci.yaml)
+[![Latest](https://img.shields.io/github/v/release/falcosecurity/pigeon)](https://github.com/falcosecurity/pigeon/releases/latest)
+[![Go Report Card](https://goreportcard.com/badge/github.com/falcosecurity/pigeon)](https://goreportcard.com/report/github.com/falcosecurity/pigeon)
+[![CI build](https://github.com/falcosecurity/pigeon/actions/workflows/ci.yaml/badge.svg)](https://github.com/falcosecurity/pigeon/actions/workflows/ci.yaml)
 
 Script to set github org/repo actions variables and secrets from a config file.  
 

diff --git a/go.mod b/go.mod
@@ -1,4 +1,4 @@
-module github.com/FedeDP/Pigeon
+module github.com/falcosecurity/pigeon
 
 go 1.17
 

diff --git a/main.go b/main.go
@@ -3,12 +3,13 @@ package main
 import (
 	"context"
 	"flag"
-	"github.com/FedeDP/Pigeon/pkg/pigeon"
-	"github.com/google/go-github/v50/github"
 	"os"
 	"strings"
 
-	"github.com/FedeDP/Pigeon/pkg/config"
+	"github.com/falcosecurity/pigeon/pkg/pigeon"
+	"github.com/google/go-github/v50/github"
+
+	"github.com/falcosecurity/pigeon/pkg/config"
 	"github.com/sirupsen/logrus"
 )
 

diff --git a/pkg/config/config.go b/pkg/config/config.go
@@ -3,10 +3,11 @@ package config
 import (
 	"context"
 	"encoding/base64"
-	"github.com/FedeDP/Pigeon/pkg/pigeon"
 	"os"
 	"strings"
 
+	"github.com/falcosecurity/pigeon/pkg/pigeon"
+
 	"github.com/google/go-github/v50/github"
 	"github.com/jamesruan/sodium"
 	"github.com/sirupsen/logrus"

diff --git a/pkg/config/config_test.go b/pkg/config/config_test.go
@@ -2,9 +2,10 @@ package config
 
 import (
 	"context"
-	"github.com/FedeDP/Pigeon/pkg/pigeon"
 	"testing"
 
+	"github.com/falcosecurity/pigeon/pkg/pigeon"
+
 	"github.com/stretchr/testify/assert"
 )
 

diff --git a/release.md b/release.md
@@ -1,13 +1,13 @@
 # Release Process
 
-Our release process is based upon [Github Actions](https://github.com/FedeDP/Pigeon/actions) and [goreleaser](https://github.com/goreleaser/goreleaser) tool for artifacts.
+Our release process is based upon [Github Actions](https://github.com/falcosecurity/pigeon/actions) and [goreleaser](https://github.com/goreleaser/goreleaser) tool for artifacts.
 
 When we release we do the following process:
 
 1. We decide together (usually in the #falco channel in [slack](https://kubernetes.slack.com/messages/falco)) what's the next version to tag
 2. A person with repository rights does the tag
 3. The same person runs commands in their machine following the "Release commands" section below
-4. Once the CI has done its job, the tag is live on [Github](https://github.com/falcosecurity/Pigeon/releases) with the artifacts
+4. Once the CI has done its job, the tag is live on [Github](https://github.com/falcosecurity/pigeon/releases) with the artifacts
 
 ## Release commands