community
community copied to clipboard
aws-controllers-k8s
Address non necessary merge/rebase conflicts in `ack-metadata.yaml`
Is your feature request related to a problem? We have no requirements for which operating system our contributors should use for development, and broadly allow Go versions 1.16+. It would be great to standardize the development version, so that we ensure each engineer has access to the latest Go features and optimisations without having to ask everyone to update.
Describe the solution you'd like I would like to put Go into a Docker container that can be transparently used as a replacement for the local Go binary. This would require wiring up all relevant Go config variables and mounting the paths as expected.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
One solution would to remove the Go version from ack-metadata.yaml to avoid merge/rebase conflicts