Skip to content

Issues: redhat-developer/odo

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

Clear current search query, filters, and sorts
16 Open 881 Closed
16 Open 881 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

Publish odo to Winget kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
#7275 opened Nov 22, 2024 by Waterstraal
Create Backstage Plugin for Odo CLI to Bootstrap Application Development with Devfiles area/backstage Issues or PRs related to the Backstage integration kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
#7091 opened Sep 20, 2023 by mohitsuman
12 of 20 tasks
4
Simplify CLI installation commands area/Linux Issues or PRs specific to Linux area/MacOS Issues or PRs specific to MacOS area/UX Issues or PRs related to User Experience area/Windows Issues or PRs specific to Windows kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
#6896 opened Jun 15, 2023 by rm3l
2
odo dev must create PVCs for all volumes defined in the Devfile area/dev Issues or PRs related to `odo dev` kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#6844 opened May 25, 2023 by feloy
4
Pass a list of architectures to support to Alizer area/analyze Issues or PRs related to `odo analyze` / Alizer kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)
#6805 opened May 9, 2023 by feloy
8
Support dedicatedPod field on container components area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
#6786 opened May 3, 2023 by rm3l
4
[Feature request] 2-way sync of source code between developer machine and container kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
#6567 opened Feb 3, 2023 by rm3l
3
A new command to add K8s component to the Devfile from file kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
#6338 opened Nov 23, 2022 by valaparthvi
4
Copy devfile.yaml dependencies when running odo init with --devfile-path kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
#5713 opened May 5, 2022 by feloy
4
export as helm chart(s) kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#4432 opened Feb 12, 2021 by langdon
3
Helm support on odo kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
#4236 opened Nov 18, 2020 by gorkem
13
Continuous testing kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3724 opened Aug 9, 2020 by gorkem
5
Present license notices from command line area/release-eng Issues or PRs related to the Release Engineering kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3035 opened Apr 28, 2020 by atgreen
4
Local development with Telepresence kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
#2840 opened Apr 7, 2020 by gorkem
11
Support projects with dockerfile kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2352 opened Nov 4, 2019 by gorkem
6
Integration with pipelines (CI) area/outerloop Issues or PRs related to outer-loop use cases kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
#1238 opened Jan 27, 2019 by sspeiche
5
ProTip! Type g i on any issue or pull request to go back to the issue listing page.