Review Git authentication on Carol apps

Description

PRDE - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

Today we don’t have visibility about the repository info (public or private) so the validation is done only when submitting all information filled, causing validation problems that could be avoided.
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):

https://www.figma.com/file/FiL1iRG6RPjuNCgVzgGqvaZ3/%F0%9F%9F%A3-Carol-3.0?type=design&node-id=34195-93871&mode=design&t=fU1jbTVBgA340A1S-4

06 - ACCEPTANCE CRITERIA:

  • First step: the user needs to inform if the repository is public or private.
    • If public, enable Next button
    • If private, the user needs to Connect with Github (screen below), and then enable Next button
  • Second step: the user needs to inform project and branch

Activity

Automation for Jira 19 December 2023, 16:09 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 December 2023, 16:09 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 December 2023, 16:09 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 December 2023, 16:09 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 December 2023, 16:09 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 15 December 2023, 21:59 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,moisesjsf.

Automation for Jira 15 December 2023, 21:59 Jira Internal Users

Github user moisesjsf has just approved a PR (added as Shard Assignee in this Jira issue).

chore(Apps): https://totvslabs.atlassian.net/browse/CAPL-4989#icft=CAPL-4989 UX review of the git connection wizard

Moises Jose Soares Filho 15 December 2023, 21:58 Jira Internal Users

This card has been validated by the QA team.

Automation for Jira 11 December 2023, 20:26 Jira Internal Users

@Robson Thanael Poffo ,
@Pedro Buzzi , @Carlos Affonso Wagner , @Andre Pasold

This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2023-12-11, 2024-01-01

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 11 December 2023, 16:27 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 10 December 2023, 14:03 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

chore(Apps): https://totvslabs.atlassian.net/browse/CAPL-4989#icft=CAPL-4989 UX review of the git connection wizard

Automation for Jira 20 November 2023, 20:44 Jira Internal Users

@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner ,

This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2023-12-11

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.