You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ In order to help us process this request faster, please provide as much detail a
14
14
Before creating a feature request, please search existing issues to see if this request has already been made. If there is a similar feature request please up-vote it and/or add your comments to it instead.
15
15
16
16
For more information on how to contribute to eksctl, please refer to our contributing docs.
Copy file name to clipboardExpand all lines: .github/workflows/greetings.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -12,5 +12,5 @@ jobs:
12
12
- uses: actions/first-interaction@v1
13
13
with:
14
14
repo-token: ${{ secrets.GITHUB_TOKEN }}
15
-
issue-message: 'Hello ${{ github.event.issue.user.login }} :wave: Thank you for opening an issue in `eksctl` project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines [here](https://github.com/weaveworks/eksctl#contributions). You can find out more information about `eksctl` on our [website](https://eksctl.io)'
16
-
pr-message: 'Hello ${{ github.event.pull_request.user.login }} :wave: Thank you for opening a Pull Request in `eksctl` project. The team will review the Pull Request and aim to respond within 1-10 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines [here](https://github.com/weaveworks/eksctl#contributions). You can find out more information about `eksctl` on our [website](https://eksctl.io)'
15
+
issue-message: 'Hello ${{ github.event.issue.user.login }} :wave: Thank you for opening an issue in `eksctl` project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines [here](https://github.com/eksctl-io/eksctl#contributions). You can find out more information about `eksctl` on our [website](https://eksctl.io)'
16
+
pr-message: 'Hello ${{ github.event.pull_request.user.login }} :wave: Thank you for opening a Pull Request in `eksctl` project. The team will review the Pull Request and aim to respond within 1-10 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines [here](https://github.com/eksctl-io/eksctl#contributions). You can find out more information about `eksctl` on our [website](https://eksctl.io)'
message: ":ahhhhhhhhh: ${{ inputs.name }} has failed for tag <https://github.com/weaveworks/eksctl/releases/tag/${{ steps.get_version.outputs.version }}|${{ steps.get_version.outputs.version }}>"
68
+
message: ":ahhhhhhhhh: ${{ inputs.name }} has failed for tag <https://github.com/eksctl-io/eksctl/releases/tag/${{ steps.get_version.outputs.version }}|${{ steps.get_version.outputs.version }}>"
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-13
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ clear, we also accept contributions to this contribution doc :smile:.
14
14
For information on how to get in touch, or how the project is run, please see
15
15
the [Community page](COMMUNITY.md).
16
16
17
-
_(If you are a Maintainer, head over to the [Maintainer's guide](https://github.com/weaveworks/eksctl-handbook).)_
17
+
_(If you are a Maintainer, head over to the [Maintainer's guide](https://github.com/eksctl-io/eksctl-handbook).)_
18
18
19
19
Reading docs is often tedious, so we'll put our most important contributing rule
20
20
right at the top: **Always be kind!**
@@ -78,9 +78,9 @@ Here is a non-exhaustive list of ways you can help out:
78
78
We have 3 forms of issue: [bug reports](#bug-report-guide), [feature requests](#feature-request-guide) and [help requests](#help-request-guide).
79
79
If you are not sure which category you need, just make the best guess and provide as much information as possible.
80
80
1. Help out others in the [eksctl slack channel](https://slack.k8s.io/messages/eksctl/). :sos:
81
-
1. Chime in on [bugs](https://github.com/weaveworks/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fbug+), [feature requests](https://github.com/weaveworks/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Ffeature) and asks for [help](https://github.com/weaveworks/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fhelp). :thought_balloon:
82
-
1. Dig into some [`needs-investigation` issues](https://github.com/weaveworks/eksctl/labels/needs-investigation):detective:
83
-
1. Get involved in some [PR reviews](https://github.com/weaveworks/eksctl/pulls). :nerd_face:
81
+
1. Chime in on [bugs](https://github.com/eksctl-io/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fbug+), [feature requests](https://github.com/eksctl-io/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Ffeature) and asks for [help](https://github.com/eksctl-io/eksctl/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fhelp). :thought_balloon:
82
+
1. Dig into some [`needs-investigation` issues](https://github.com/eksctl-io/eksctl/labels/needs-investigation):detective:
83
+
1. Get involved in some [PR reviews](https://github.com/eksctl-io/eksctl/pulls). :nerd_face:
84
84
1. Review old issues; poke or suggest closing ones which are stale or follow up those which still look good. :speech_balloon:
85
85
1. Think deeply about the future of `eksctl`, then [talk about it](#proposals). :crystal_ball:
86
86
@@ -236,7 +236,7 @@ If you are not here to report a bug, ask for help or request some new behaviour,
236
236
is the section for you. We have curated a set of issues for anyone who simply
237
237
wants to build up their open-source cred :muscle:.
238
238
239
-
- Issues labelled [`good first issue`](https://github.com/weaveworks/eksctl/labels/good%20first%20issue)
239
+
- Issues labelled [`good first issue`](https://github.com/eksctl-io/eksctl/labels/good%20first%20issue)
240
240
should be accessible to folks new to the repo, as well as to open source in general.
241
241
242
242
These issues should present a low/non-existent barrier to entry with a thorough description,
@@ -252,7 +252,7 @@ wants to build up their open-source cred :muscle:.
252
252
253
253
See more on [asking for help](#asking-for-help) below!
are for those a little more familiar with the code base, but should still be accessible enough
257
257
to newcomers.
258
258
@@ -422,15 +422,15 @@ tests you can get to work :tada: .
422
422
423
423
1. Write your solution. Try to align with existing patterns and standards.
424
424
_However_, there is significant tech debt, so any refactoring or changes which would
425
-
improve things even a little would be very welcome. (See [#2931](https://github.com/weaveworks/eksctl/issues/2931)
425
+
improve things even a little would be very welcome. (See [#2931](https://github.com/eksctl-io/eksctl/issues/2931)
426
426
for our current efforts.)
427
427
428
428
1. Try to commit in small chunks so that changes are well described
429
429
and not lumped in with something unrelated. This will make debugging easier in
430
430
the future.
431
431
Make sure commit messages are in the [proper format](#commit-message-formatting).
432
432
433
-
1. Be sure to include at least unit tests to cover your changes. See the [addon](https://github.com/weaveworks/eksctl/blob/main/pkg/actions/addon)
433
+
1. Be sure to include at least unit tests to cover your changes. See the [addon](https://github.com/eksctl-io/eksctl/blob/main/pkg/actions/addon)
434
434
package for a good example of tests.
435
435
436
436
> NOTE: We are trying to move away from using [`mockery`](https://github.com/vektra/mockery)
@@ -591,7 +591,7 @@ The core team regularly processes incoming issues. There may be some delay over
591
591
592
592
Every issue will be assigned a `priority/<x>` label. The levels of priorities are:
593
593
594
-
-[`critical`](https://github.com/weaveworks/eksctl/labels/priority%2Fcritical): These are time sensitive issues which should be picked up immediately.
594
+
-[`critical`](https://github.com/eksctl-io/eksctl/labels/priority%2Fcritical): These are time sensitive issues which should be picked up immediately.
595
595
If an issue labelled `critical` is not assigned or being actively worked on,
596
596
someone is expected to drop what they're doing immediately to work on it.
597
597
This usually means the core team, but community members are welcome to claim
@@ -600,18 +600,18 @@ Every issue will be assigned a `priority/<x>` label. The levels of priorities ar
600
600
they will be paired with a core team-member to manage the tracking, communication and release of any fix
601
601
as well as to assume responsibility of all progess._
602
602
603
-
-[`important-soon`](https://github.com/weaveworks/eksctl/labels/priority%2Fimportant-soon): Must be assigned as soon as capacity becomes available.
603
+
-[`important-soon`](https://github.com/eksctl-io/eksctl/labels/priority%2Fimportant-soon): Must be assigned as soon as capacity becomes available.
604
604
Ideally something should be delivered in time for the next release.
605
605
606
-
-[`important-longterm`](https://github.com/weaveworks/eksctl/labels/priority%2Fimportant-longterm): Important over the long term, but may not be currently
606
+
-[`important-longterm`](https://github.com/eksctl-io/eksctl/labels/priority%2Fimportant-longterm): Important over the long term, but may not be currently
607
607
staffed and/or may require multiple releases to complete.
608
608
609
-
-[`backlog`](https://github.com/weaveworks/eksctl/labels/priority%2Fbacklog): There appears to be general agreement that this would be good to have,
609
+
-[`backlog`](https://github.com/eksctl-io/eksctl/labels/priority%2Fbacklog): There appears to be general agreement that this would be good to have,
610
610
but we may not have anyone available to work on it right now or in the immediate future.
611
611
PRs are still very welcome, although it might take a while to get them reviewed if
612
612
reviewers are fully occupied with higher priority issues, for example immediately before a release.
613
613
614
-
-[`needs-investigation`](https://github.com/weaveworks/eksctl/labels/needs-investigation): There is currently insufficient information to either categorize properly,
614
+
-[`needs-investigation`](https://github.com/eksctl-io/eksctl/labels/needs-investigation): There is currently insufficient information to either categorize properly,
615
615
or to understand and implement a solution. This could be because the issue opener did
616
616
not provide enough relevant information, or because more in-depth research is required
`eksctl` is a simple CLI tool for creating clusters on EKS - Amazon's new managed Kubernetes service for EC2. It is written in Go, and uses CloudFormation.
6
6
@@ -23,10 +23,10 @@ To download the latest release, run:
@@ -226,7 +226,7 @@ Do not open security related issues in the open source project.
226
226
227
227
## Get in touch
228
228
229
-
[Create an issue](https://github.com/weaveworks/eksctl/issues/new), or login to [Eksctl Community Slack (#eksctl)][slackchan] ([signup][slackjoin]).
229
+
[Create an issue](https://github.com/eksctl-io/eksctl/issues/new), or login to [Eksctl Community Slack (#eksctl)][slackchan] ([signup][slackjoin]).
0 commit comments