Skip to content
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.

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

Always allow component creation if dockerfile runtime is selected #730

Merged

Conversation

rottencandy
Copy link
Contributor

@rottencandy rottencandy commented Jul 21, 2023

Fixes

https://issues.redhat.com/browse/RHTAPBUGS-469

Description

Always allow component creation if dockerfile runtime is selected.

Type of change

  • Feature
  • Bugfix
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Screen shots / Gifs for design review

recording-1690205082.mp4

How to test or reproduce?

Use a repo that returns error when detection, and select dockerfile runtime.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 21, 2023
@rottencandy rottencandy force-pushed the fix/dockerfile-enable-469 branch 2 times, most recently from 0feeef0 to 5c64d6c Compare July 24, 2023 13:45
@rottencandy rottencandy changed the title [WIP] Always allow component creation if dockerfile runtime is selected Always allow component creation if dockerfile runtime is selected Jul 24, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 24, 2023
@rottencandy
Copy link
Contributor Author

/retest

@jrichter1
Copy link
Contributor

/test test

@codecov
Copy link

codecov bot commented Jul 25, 2023

Codecov Report

Merging #730 (966c045) into main (a329ef5) will increase coverage by 0.60%.
Report is 48 commits behind head on main.
The diff coverage is 93.75%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #730      +/-   ##
==========================================
+ Coverage   83.62%   84.23%   +0.60%     
==========================================
  Files         499      499              
  Lines       12295    12954     +659     
  Branches     3521     3836     +315     
==========================================
+ Hits        10282    10912     +630     
- Misses       1896     1924      +28     
- Partials      117      118       +1     
Files Changed Coverage Δ
...ponents/ImportForm/ReviewSection/ReviewSection.tsx 81.55% <0.00%> (+1.86%) ⬆️
...nents/ImportForm/ReviewSection/RuntimeSelector.tsx 98.19% <100.00%> (+1.00%) ⬆️

... and 27 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a329ef5...966c045. Read the comment docs.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 30, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 31, 2023
@rottencandy
Copy link
Contributor Author

/retest

@rohitkrai03
Copy link
Contributor

Even after selecting Dockerfile runtime the create button doesn't get enabled. I have to touch the dockerfile and port fields to enable it.

Screen.Recording.2023-08-03.at.9.09.29.PM.mov

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 3, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 4, 2023
@rottencandy
Copy link
Contributor Author

Looks like that was the bug which was fixed in #739, I rebased and it's working fine now.

@rottencandy
Copy link
Contributor Author

/cc @rohitkrai03 @karthikjeeyar

Copy link
Contributor

@rohitkrai03 rohitkrai03 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 22, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 22, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rohitkrai03, rottencandy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 22, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 22, 2023

@rottencandy: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 66d6a47 into openshift:main Aug 22, 2023
2 checks passed
@rottencandy rottencandy deleted the fix/dockerfile-enable-469 branch September 28, 2023 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants