Skip to content

Issues: octomation/go-service

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.

Sign up for GitHub

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

18 Open 54 Closed
18 Open 54 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

deps: broken go.mod effort: easy An issue is easy to implement. impact: low An issue has low impact. scope: deps An issue related to dependencies. severity: minor A bug has minor severity and should be fixed when possible. type: bug A new bug report.
#306 opened Aug 17, 2024 by kamilsk Ready to go, v1.0
@kamilsk
ci/cd: broken builds effort: easy An issue is easy to implement. impact: high An issue has high impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. severity: major A bug has major severity and needs to be fixed in the nearest iteration. type: bug A new bug report.
#173 opened Nov 21, 2023 by kamilsk
2 tasks
Ready to go, v1.0
@kamilsk
dev: gitops with argocd and crossplane effort: hard An issue is hard to implement or reproduce. impact: high An issue has high impact. scope: code An issue related to source code. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. status: pending Mark an issue as hold. type: feature A new feature request.
#109 opened Jun 20, 2023 by kamilsk Ready to scale, v1.1
@kamilsk
dev: support code coverage for integration tests effort: medium An issue has a medium complexity. impact: high An issue has high impact. scope: code An issue related to source code. scope: test An issue related to tests. type: improvement A new improvement proposal.
#98 opened Mar 9, 2023 by kamilsk Ready to scale, v1.1
@kamilsk
1
dev: env: try okteto effort: medium An issue has a medium complexity. impact: high An issue has high impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: feature A new feature request.
#76 opened Oct 31, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
dev: protobuf: support Buf Studio effort: medium An issue has a medium complexity. impact: medium An issue has medium impact. scope: code An issue related to source code. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: feature A new feature request.
#75 opened Oct 30, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
dev: use cdk8s for k8s effort: medium An issue has a medium complexity. impact: high An issue has high impact. scope: code An issue related to source code. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: feature A new feature request.
#72 opened Oct 26, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
ci/cd: sign commits from goreleaser effort: medium An issue has a medium complexity. impact: high An issue has high impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: improvement A new improvement proposal.
#55 opened Aug 12, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
ci/cd: add linter for dotenv
#53 opened Aug 6, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
boilerplate: fetch latest changes from go-tool effort: easy An issue is easy to implement. impact: high An issue has high impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: feature A new feature request.
#50 opened Aug 3, 2022 by kamilsk Ready to go, v1.0
@kamilsk
boilerplate: bootstrap: quick usage examples and best practices effort: hard An issue is hard to implement or reproduce. impact: medium An issue has medium impact. scope: docs An issue related to documentation. type: improvement A new improvement proposal.
#45 opened May 26, 2022 by kamilsk
3 tasks
Ready to go, v1.0
@kamilsk
1
dev: add k8s
#43 opened May 25, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
docs: readme: describe template and its purpose effort: hard An issue is hard to implement or reproduce. impact: high An issue has high impact. scope: docs An issue related to documentation. type: improvement A new improvement proposal.
#41 opened May 25, 2022 by kamilsk Ready to go, v1.0
@kamilsk
specs: codegen: smokes: integrate apideck/portman
#34 opened Apr 26, 2022 by kamilsk Ready to scale, v1.1
@kamilsk
boilerplate: define health endpoint
#30 opened Mar 27, 2022 by kamilsk
9 tasks
Ready to scale, v1.1
@kamilsk
boilerplate: codegen: smokes: configure tools and automate process effort: easy An issue is easy to implement. impact: medium An issue has medium impact. scope: code An issue related to source code. scope: test An issue related to tests. type: improvement A new improvement proposal.
#25 opened Mar 15, 2022 by kamilsk
3 tasks
Ready to go, v1.0
@kamilsk
dist: support docker publishing effort: easy An issue is easy to implement. impact: high An issue has high impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: feature A new feature request.
#18 opened Dec 3, 2021 by kamilsk Ready to go, v1.0
@kamilsk
1
dist: docker: compare distroless image with alpine effort: medium An issue has a medium complexity. impact: medium An issue has medium impact. scope: inventory An issue related to auxiliary code, e.g., CI config, Makefiles, etc. type: improvement A new improvement proposal.
#6 opened Apr 1, 2021 by kamilsk Ready to go, v1.0
@kamilsk
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.