Remove augmentationProperties from Config type

[mbg]

This PR updates sendCompletedStatusReport to use the computed packs from computedConfig rather than computing the packs from the input UserConfig and AugmentationProperties locally.

As a result, AugmentationProperties is no longer needed in Config and is removed.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

Pull Request Overview

This PR removes the augmentationProperties field from the Config type by updating sendCompletedStatusReport to use computed packs from computedConfig instead of calculating them from UserConfig and AugmentationProperties. The change simplifies the configuration interface while maintaining the same functionality.

Key changes:

• Removed augmentationProperties from the Config type definition
• Updated getDefaultConfig return type to temporarily include augmentationProperties for internal use
• Simplified pack calculation logic in sendCompletedStatusReport to use computedConfig.packs directly

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/config-utils.ts	Removes augmentationProperties from Config type and updates getDefaultConfig return type
src/init-action.ts	Simplifies pack calculation logic to use config.computedConfig.packs directly
src/testing-utils.ts	Removes augmentationProperties import and removes the field from test config creation
src/config-utils.test.ts	Updates test to destructure augmentationProperties from getDefaultConfig result
src/codeql.test.ts	Updates test to pass augmentationProperties directly to generateCodeScanningConfig
lib/init-action.js	Generated JavaScript file (not reviewed per guidelines)

[henrymercer]

Before merging, could you run some of the PR checks that include packs in debug mode and check that the packs property is populated correctly?

[henrymercer]

Given that we only use getDefaultConfig in this function, consider having getDefaultConfig populate computedConfig directly to simplify the flow.

[mbg]

I have made the UserConfig (from the inputs) an argument to getDefaultConfig (now initActionState), set it there, and generate computedConfig there. That avoids having to return augmentationProperties as well.

[mbg]

@henrymercer I refactored creating the InitWithConfigStatusReport into a function and added some unit tests for that. That should be more robust than checking the debug logs, but let me know if you still want me to do that as well?

[henrymercer]

Great, even better!