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.

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

Jump to bottom

[Issue] gitignore for files and folders generated by Magento Functional Testing Framework (MFTF) #30135

Open
4 tasks
m2-assistant bot opened this issue Sep 21, 2020 · 0 comments · May be fixed by #30107
Open
4 tasks

[Issue] gitignore for files and folders generated by Magento Functional Testing Framework (MFTF) #30135

m2-assistant bot opened this issue Sep 21, 2020 · 0 comments · May be fixed by #30107
Labels
Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR in progress Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Low Priority Backlog

Comments

@m2-assistant
Copy link

m2-assistant bot commented Sep 21, 2020

This issue is automatically created based on existing pull request: #30107: gitignore for files and folders generated by Magento Functional Testing Framework (MFTF)

Description (*)

When we execute the commands related on https://devdocs.magento.com/mftf/docs/commands/mftf.html

Folders and files will be created during execution of MFTF commands.

In my opinion the changes on those folders and files should not be staged for commit.

image

Related Pull Requests

N/A

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

  1. vendor/bin/mftf build:project
  2. vendor/bin/mftf generate:tests

Questions or comments

N/A

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)
@m2-assistant m2-assistant bot added Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Sep 21, 2020
@m2-assistant m2-assistant bot linked a pull request Sep 21, 2020 that will close this issue
Open
5 tasks
@ghost ghost added this to Ready for QA in Community Backlog Sep 21, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Sep 21, 2020
@ghost ghost moved this from Ready for QA to PR In Progress in Community Backlog Sep 21, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov removed this from Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Pull Request In Progress in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR in progress labels Sep 24, 2020
@ghost ghost unassigned lfluvisotto Oct 19, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Oct 19, 2020
@ghost ghost unassigned lfluvisotto Nov 13, 2020
@m2-community-project m2-community-project bot removed this from PR In Progress in Community Backlog Nov 13, 2020
@m2-community-project m2-community-project bot added Progress: PR in progress and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Nov 13, 2020
@engcom-Dash engcom-Dash added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR in progress Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Low Priority Backlog
  
Pull Request In Progress
Milestone
No milestone
3 participants
@lfluvisotto @magento-engcom-team @engcom-Dash