Replace keyphrase validation with file modification detection in step 3 grading

[Copilot]

• Review current workflow implementation in 3-copilot-edits.yml
• Replace keyphrase checker steps with tj-actions/changed-files action
• Add step to detect changed files compared to main branch
• Add individual validation steps for app.js modification
• Add individual validation steps for styles.css modification
• Verify the workflow syntax is valid
• Use any_changed output for precise file matching
• Run final validation and testing
• Complete code review with no issues
• Pass security scan with no vulnerabilities
• Simplify to use github.event.repository.default_branch
• Reference tj-actions outputs directly in results table
• Use base_sha parameter name (not base)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Bug] Cannot move throw the step 3</issue_title>
<issue_description>### Summary

I am in the step 3 Step 3: Getting work done even faster with Copilot Edit Mode
I do all the steps in the comment and push the code, but I cannot pass the exam. I am sure that I already pushed 2 files: app.js, styles.css

How to reproduce

In step 3, push the code for the GitHub Action check

But only app.js passed ✅

Is this a bug? I try to push again, but I still fail. What happened to me?

</issue_description>

<agent_instructions>Replace the grading in step 3 to only check if the files were modified (compare to main branch) - use https://github.com/tj-actions/changed-files for the checking of what files changed compared to main branch and 2 individual steps to check the output of changed files for each file </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@FidelusAleksander Hey @hoangngoclam

Thanks for raising the issue! The automation checks for participant keywords in the css and js files

I think we will have to redesign that check to be more lenient, as you clearly have done what was asked.

Before this is updated, in your exercise you can just make sure participant keyword is used in the styles.css at least once</comment_new>

• Fixes [Bug] Cannot move throw the step 3 skills/getting-started-with-github-copilot#111

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[FidelusAleksander]

@copilot Actually the default branch can be used for base_sha parameter even though it is not technically sha

base_sha: ${{ github.event.repository.default_branch }}

Let's use tj-actions/changed-files for each file and then in the results table reference the output directly for the passed parameter

[Copilot]

@copilot Actually the default branch can be used for base_sha parameter even though it is not technically sha

base_sha: ${{ github.event.repository.default_branch }}
...

Updated the workflow as suggested. Changes made in commit c004bbe:

• Removed the "Fetch main branch" step
• Simplified by using base: ${{ github.event.repository.default_branch }} parameter
• Removed intermediate shell script checks
• Referenced any_changed output directly in the results table's passed parameter
• Updated fail condition to check the outputs directly

The workflow is now much cleaner with 29 fewer lines while maintaining the same functionality.

[FidelusAleksander]

@copilot the parameter should name still be base_sha

[Copilot]

@copilot the parameter should name still be base_sha

Fixed in commit ecf119c. Changed the parameter back to base_sha as you indicated.