Fix linter flow not triggered (microsoft#897)

* testcraft got rebranded to perfecto.

* We get 403 from perfecto, they might have blocked bots as the site is working ...

* ignore ranorex

* [MegaLinter] Apply linters fixes

* Update mega-linter.yml

Remove master

* fix linter

* Update mega-linter.yml

Fix lintrer

* Update mega-linter.yml

Fix linter

* Update mega-linter.yml

Co-authored-by: shiranr <[email protected]>

Author: shiranr

.cspell.json

@@ -424,9 +424,10 @@
     "zstd",
     "Apdex",
     "Aur\u00e9lien",
-    "Avi\u02c7zienis",
+    "Avi",
+    "zienis",
     "Customizabile",
-    "Dodd\u2019s",
+    "Dodd's",
     "G\u00e9ron's"
   ],
   "version": "0.2"

.github/workflows/mega-linter.yml

@@ -7,7 +7,7 @@ on:
   # Trigger mega-linter at every push. Action will also be visible from pull requests to main
   push: # Comment this line to trigger action only on pull-requests (not recommended if you don't pay for GH Actions)
   pull_request:
-    branches: [master, main]
+    branches: [main]
 
 env: # Comment env block if you do not want to apply fixes
   # Apply linter fixes configuration

.markdown-link-check.json

@@ -20,7 +20,8 @@
     {"pattern": "^https://www.researchgate.net/publication/301839557_The_landscape_of_software_failure_cause_models"},
     {"pattern": "^https://www.cmu.edu/iso/governance/guidelines/data-classification.html"},
     {"pattern": "^https://machinelearningmastery.com/how-to-get-baseline-results-and-why-they-matter/"},
-    {"pattern": "^https://www.perfecto.io/"}
+    {"pattern": "^https://www.perfecto.io/"},
+    {"pattern": "^https://www.ranorex.com/free-trial/"}
   ],
   "httpHeaders": [
     {

docs/automated-testing/e2e-testing/README.md

@@ -159,11 +159,11 @@ Katalon is endorsed by Gartner, IT professionals, and a large testing community.
 
 ![BugBug](./images/bugbug-logo-208x65.png)
 
-**BugBug** is an easy way to automate tests for web applications. The tool focuses on simplicity, yet allows you to cover all essential test cases without coding. It's an all-in-one solution - you can easily create tests and use the built-in cloud to run them on schedule or from your CI/CD, without changes to your own infrastructure. 
+**BugBug** is an easy way to automate tests for web applications. The tool focuses on simplicity, yet allows you to cover all essential test cases without coding. It's an all-in-one solution - you can easily create tests and use the built-in cloud to run them on schedule or from your CI/CD, without changes to your own infrastructure.
 
-BugBug is an interesting alternative to Selenium because it's actually a completely different technology. It is based on a Chrome extension that allows BugBug to record and run tests faster than old-school frameworks. 
+BugBug is an interesting alternative to Selenium because it's actually a completely different technology. It is based on a Chrome extension that allows BugBug to record and run tests faster than old-school frameworks.
 
-The biggest advantage of BugBug is its user-friendliness. Most tests created with BugBug simply work out of the box. This makes it easier for non-technical people to maintain tests - with BugBug you can save money on hiring a QA engineer. 
+The biggest advantage of BugBug is its user-friendliness. Most tests created with BugBug simply work out of the box. This makes it easier for non-technical people to maintain tests - with BugBug you can save money on hiring a QA engineer.
 
 [BugBug Website](https://bugbug.io?utm_source=microsoft_github&utm_medium=referral)
 

docs/machine-learning/ml-feasibility-study.md

@@ -1,10 +1,10 @@
 # Feasibility Studies
 
 The main goal of feasibility studies is to assess whether it is feasible to solve the problem satisfactorily using ML with the available data. We want to avoid investing too much in the solution before we have:
-*	Sufficient evidence that a solution would be the best technical solution given the business case
-*	Sufficient evidence that a solution is compatible with the problem context
-*	Sufficient evidence that a solution is possible
-*	Some vetted direction on what a solution should look like
+* Sufficient evidence that a solution would be the best technical solution given the business case
+* Sufficient evidence that a solution is compatible with the problem context
+* Sufficient evidence that a solution is possible
+* Some vetted direction on what a solution should look like
 This effort ensures quality solutions backed by the appropriate, thorough amount of consideration and evidence.
 
 ## When are feasibility studies useful?
@@ -23,25 +23,25 @@ Collaboration from individuals with diverse skill sets is desired at this stage,
 
 ### Problem definition and desired outcome
 
-*	Ensure that the problem is complex enough that coding rules or manual scaling is unrealistic
-*	Clear definition of the problem from business and technical perspectives
+* Ensure that the problem is complex enough that coding rules or manual scaling is unrealistic
+* Clear definition of the problem from business and technical perspectives
 
 ### Deep contextual understanding
 
 Confirm that the following questions can be answered based on what was learned during the Discovery Phase of the project. For items that can not be satisfactorily answered, undertake additional investigation to answer.
-*	Understanding the people who are using and/or affected by the solution
-*	Understanding the contextual forces at play around the problem, including goals, culture, and historical context
-*	To accomplish this a researcher will:
-  *	Collaborate with customers and colleagues to explore the landscape of people who relate to and may be affected by the problem space being explored (Users, stakeholders, subject matter experts, etc)
-  *	Formulate the research question(s) to be addressed
-  *	Select and design research to best serve the research question(s) 
-  *	Identify and select representative research participants across the problem space with whom to conduct the research
-  *	Construct a research plan and necessary preparation documents for the selected research method(s)
-  *	Conduct research activity with the participants via the selected method(s)
-  *	Synthesize, analyze, and interpret research findings
-  *	Where relevant, build frameworks, artefacts and processes that help explore the findings and implications of the research across the team
-  *	Share what was uncovered and understood, and the implications thereof across the engagement team and relevant stakeholders.
-*	If the above research was conducted during the Discovery phase, it should be reviewed, and any substantial knowledge gaps should be identified and filled by following the above process.
+* Understanding the people who are using and/or affected by the solution
+* Understanding the contextual forces at play around the problem, including goals, culture, and historical context
+* To accomplish this a researcher will:
+* Collaborate with customers and colleagues to explore the landscape of people who relate to and may be affected by the problem space being explored (Users, stakeholders, subject matter experts, etc)
+* Formulate the research question(s) to be addressed
+* Select and design research to best serve the research question(s)
+* Identify and select representative research participants across the problem space with whom to conduct the research
+* Construct a research plan and necessary preparation documents for the selected research method(s)
+* Conduct research activity with the participants via the selected method(s)
+* Synthesize, analyze, and interpret research findings
+* Where relevant, build frameworks, artefacts and processes that help explore the findings and implications of the research across the team
+* Share what was uncovered and understood, and the implications thereof across the engagement team and relevant stakeholders.
+* If the above research was conducted during the Discovery phase, it should be reviewed, and any substantial knowledge gaps should be identified and filled by following the above process.
 
 ### Data access
 
@@ -69,13 +69,13 @@ Confirm that the following questions can be answered based on what was learned d
 
 ### Concept ideation and iteration
 
-*	Develop value proposition(s) for users and stakeholders based on the contextual understanding developed through the discovery process (e.g. key elements of value, benefits)
-*	As relevant, make use of
-  *	Co-creation with team 
-  *	Co-creation with users and stakeholders
-*	As relevant, create vignettes, narratives or other materials to communicate the concept
-*	Identify the next set of hypotheses or unknowns to be tested (see concept testing)
-*	Revisit and iterate on the concept throughout discovery as understanding of the problem space evolves
+* Develop value proposition(s) for users and stakeholders based on the contextual understanding developed through the discovery process (e.g. key elements of value, benefits)
+* As relevant, make use of
+* Co-creation with team
+* Co-creation with users and stakeholders
+* As relevant, create vignettes, narratives or other materials to communicate the concept
+* Identify the next set of hypotheses or unknowns to be tested (see concept testing)
+* Revisit and iterate on the concept throughout discovery as understanding of the problem space evolves
 
 ### Exploratory data analysis (EDA)
 
@@ -106,13 +106,13 @@ Confirm that the following questions can be answered based on what was learned d
 
 ### Concept testing
 
-*	Where relevant, to test the value proposition, concepts or aspects of the experience
-  *	Plan user, stakeholder and expert research
-  *	Develop and design necessary research materials 
-  *	Synthesize and evaluate feedback to incorporate into concept development
-*	Continue to iterate and test different elements of the concept as necessary, including testing to best serve RAI goals and guidelines
-*	Ensure that the proposed solution and framing are compatible with and acceptable to affected people
-*	Ensure that the proposed solution and framing is compatible with existing business goals and context
+* Where relevant, to test the value proposition, concepts or aspects of the experience
+* Plan user, stakeholder and expert research
+* Develop and design necessary research materials
+* Synthesize and evaluate feedback to incorporate into concept development
+* Continue to iterate and test different elements of the concept as necessary, including testing to best serve RAI goals and guidelines
+* Ensure that the proposed solution and framing are compatible with and acceptable to affected people
+* Ensure that the proposed solution and framing is compatible with existing business goals and context
 
 ### Risk assessment
 
@@ -121,9 +121,9 @@ Confirm that the following questions can be answered based on what was learned d
 ### Responsible AI
 
 * Consideration of responsible AI principles
-*	Understanding of users and stakeholders’ contexts, needs and concerns to inform development of RAI
-*	Testing AI concept and experience elements with users and stakeholders
-*	Discussion and feedback from diverse perspectives around any responsible AI concerns
+* Understanding of users and stakeholders’ contexts, needs and concerns to inform development of RAI
+* Testing AI concept and experience elements with users and stakeholders
+* Discussion and feedback from diverse perspectives around any responsible AI concerns
 
 
 ## Output of a feasibility study

docs/observability/tools/OpenTelemetry.md

@@ -92,7 +92,7 @@ Java OpenTelemetry instrumentation provides another way to integrate with Azure
 
 When configuring this option, the Applications Insights Agent file is added when executing the application. The `applicationinsights.json` configuration file must be also be added as part of the applications artifacts. Pay close attention to the preview section, where the `"openTelemetryApiSupport": true,` property is set to true, enabling the agent to intercept OpenTelemetry telemetry created in the application code pushing it to Azure Monitor.
 
-OpenTelemetry Java Agent instrumentation supports many [libraries and frameworks and application servers](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md#supported-libraries-frameworks-application-servers-and-jvms). Application Insights Java Agent [enhances](https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent#auto-instrumentation) this list. 
+OpenTelemetry Java Agent instrumentation supports many [libraries and frameworks and application servers](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md#supported-libraries-frameworks-application-servers-and-jvms). Application Insights Java Agent [enhances](https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent#auto-instrumentation) this list.
 Therefore, the main difference between running the OpenTelemetry Java Agent vs. the Application Insights Java Agent is demonstrated in the amount of traces getting logged in Azure Monitor. When running with Application Insights Java agent there's more telemetry getting pushed to Azure Monitor. On the other hand, when running the solution using the Application Insights agent mode, it is essential to highlight that nothing gets logged on Jaeger (or any other OpenTelemetry exporter). All traces will be pushed exclusively to Azure Monitor. However, both manual instrumentation done via the OpenTelemetry SDK and all automatic traces, dependencies, performance counters, and metrics being instrumented by the Application Insights agent are sent to Azure Monitor. Although there is a rich amount of additional data automatically instrumented by the Application Insights agent, it can be deduced that it is not necessarily OpenTelemetry compliant. Only the traces logged by the manual instrumentation using the OpenTelemetry SDK are.
 
 #### OpenTelemetry vs Application Insights agents compared