Skip to content

fix: Updated the build Scripts , and workflows to successful build.#62

Merged
drtechie merged 3 commits intoPSMRI:developfrom
Zapper9982:bugfix/issue-55
Apr 9, 2025
Merged

fix: Updated the build Scripts , and workflows to successful build.#62
drtechie merged 3 commits intoPSMRI:developfrom
Zapper9982:bugfix/issue-55

Conversation

@Zapper9982
Copy link
Copy Markdown
Contributor

@Zapper9982 Zapper9982 commented Apr 3, 2025

📋 Description

JIRA ID: N/A

GitHub Issue: Fixes PSMRI/AMRIT#55

Changes Made :

  • Updated the submodule to the latest commit.

  • GitHub Actions: Build on Pull Request

    • Updated .github/workflows/build-on-pull-request.yml to properly handle submodules during the build.
  • GitHub Actions: Package Workflow

    • Replaced deprecated actions/upload-artifact@v2 with actions/upload-artifact@v3 in .github/workflows/package.yml.
  • Prebuild Command:

    • Updated package.json to introduce a prebuild command that sets up the environment before running the build process.
  • Consistent Build Handling:

    • Applied the same prebuild logic to the following scripts:
      • build-ci
      • build-prod
      • build-dev
      • build-test
  • Production File Replacement:

    • Updated angular.json to implement fileReplacements for production builds.
  • fixed Minor issue of wrong reference getSessionExistsURL in src/app/app-modules/core/services/auth.service.ts


✅ Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • New feature (non-breaking change which adds functionality)
  • 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 🛠 Refactor (change that is neither a fix nor a new feature)
  • ⚙️ Config change (configuration file or build script updates)
  • 📚 Documentation (updates to docs or readme)
  • 🧪 Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • 🚀 Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Testing :

  • All github workflow commands were run locally on system to check if build works.
  • Ran the build commands and fixed the requirement of environment.ts

Screenshots

  • npm run build works successfully.
image

Summary by CodeRabbit

  • Chores

    • Enhanced automation and build processes with improved submodule handling, environment file verification, production-specific configuration, and dependency/version updates.
    • Added a new entry to .gitignore to exclude src/environments/environment.ci.ts from version control.
  • Refactor

    • Updated the user session management integration to utilize a newer endpoint for improved session validation.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 3, 2025

Walkthrough

This pull request updates several configuration and workflow files to improve the CI/CD process. GitHub Actions workflows are modified to handle submodules automatically by renaming and adding steps for manual updating. The submodule settings in the repository are adjusted, including updating URLs and commit references. Build configurations have been enhanced in Angular and package scripts by adding a prebuild check for the environment file and updating dependencies. A minor service change redirects an HTTP call to a new endpoint.

Changes

File(s) Change Summary
.github/workflows/build-on-pull-request.yml
.github/workflows/package.yml
Renamed checkout step and enabled submodules in checkout; added step to manually update submodules. Updated actions/upload-artifact version from v2 to v4 and other actions to their latest versions.
.gitmodules
Common-UI
Removed the trailing .git from the submodule URL and updated the subproject commit hash.
angular.json Added fileReplacements in the production build configuration and removed the namedChunks property from the development configuration.
package.json Introduced a new prebuild script to ensure the environment file exists; updated build scripts (including build-ci) to include this check; changed TypeScript version specification to allow minor updates.
scripts/ci-prebuild.js Added a new property SESSION_STORAGE_ENC_KEY to the default environment values.
src/app/app-modules/core/services/auth.service.ts Modified the getUserDetails method to send an HTTP POST request to a new URL (environment.getSessionExistsURL) instead of environment.getUserAuth.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Pipeline
    participant Repo as Repository
    participant Prebuild as Prebuild Script
    participant Angular as Angular Build

    CI->>Repo: Checkout code with submodules
    Note over CI,Repo: Automatic and manual submodule updates applied
    CI->>Prebuild: Run prebuild step (check/create environment file)
    Prebuild-->>CI: Prebuild completion confirmation
    CI->>Angular: Execute ng build command (build-ci)
    Angular-->>CI: Return build results
Loading

Assessment against linked issues

Objective Addressed Explanation
Ensure CI pipeline runs successfully with proper submodules initialization [#55]
Ensure the CI build command (npm run build:ci) runs using the correct Node.js version [#55] Node version is not explicitly updated; relies on existing config.

Poem

I'm a rabbit with a codey twist,
Hopping through repos with a joyful tryst,
Submodules in line and builds so neat,
Prebuilds ensuring no file is beat—
With carrots 🥕 and clean commits in sight,
My whiskered heart hops with pure delight!
CodeRabbit cheers this PR day and night!


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
.github/workflows/package.yml (1)

47-47: Good update to actions/upload-artifact@v3

Updating to the newer version of the upload-artifact action is beneficial for improved features and security. There's a trailing space at the end of this line that should be removed for better code cleanliness.

-      uses: actions/upload-artifact@v3 
+      uses: actions/upload-artifact@v3
🧰 Tools
🪛 actionlint (1.7.4)

47-47: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)

[error] 47-47: trailing spaces

(trailing-spaces)

.github/workflows/build-on-pull-request.yml (1)

11-16: Good improvement to submodule handling in checkout

Renaming the step and adding the submodules: true parameter ensures that submodules are automatically checked out during the build process, which aligns with the PR objectives for proper submodule handling.

-          submodules: true  
+          submodules: true
🧰 Tools
🪛 actionlint (1.7.4)

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)

[error] 16-16: trailing spaces

(trailing-spaces)

package.json (1)

7-8: Prebuild Script for Environment Setup.
The introduction of the prebuild script, which checks for the existence of src/environments/environment.ts and creates it if missing, is a useful safeguard to prevent build failures. As a nitpick, please verify cross-platform compatibility—this shell syntax works on Unix-like systems but may need adjustments for Windows environments (or a note in the README to advise using a compatible shell).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 888ff12 and 8cfb9f8.

📒 Files selected for processing (8)
  • .github/workflows/build-on-pull-request.yml (1 hunks)
  • .github/workflows/package.yml (1 hunks)
  • .gitmodules (1 hunks)
  • Common-UI (1 hunks)
  • angular.json (1 hunks)
  • package.json (3 hunks)
  • scripts/ci-prebuild.js (1 hunks)
  • src/app/app-modules/core/services/auth.service.ts (1 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/package.yml

47-47: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/build-on-pull-request.yml

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)
.github/workflows/package.yml

[error] 47-47: trailing spaces

(trailing-spaces)

.github/workflows/build-on-pull-request.yml

[error] 16-16: trailing spaces

(trailing-spaces)

🔇 Additional comments (11)
.gitmodules (1)

3-3: Submodule URL Updated Correctly

The removal of the .git suffix aligns with the updated GitHub workflows and submodule handling, ensuring that the proper repository version is checked out during builds.

Common-UI (1)

1-1: Submodule Commit Update Validated.

The submodule commit has been updated to 71a223686e9f4bae4e425be286d362a23998cb2a. Ensure that this update has been tested so that it integrates smoothly with the main repository.

scripts/ci-prebuild.js (1)

46-46: Good addition of SESSION_STORAGE_ENC_KEY to default environment values

This addition allows for configuration of the session storage encryption key through environment variables, which is good practice for security-related settings across different deployment environments.

src/app/app-modules/core/services/auth.service.ts (1)

51-51: Fixed endpoint reference for getUserDetails method

The change correctly updates the endpoint to use getSessionExistsURL instead of the previous incorrect reference, aligning with the PR objectives. The method now properly checks for existing sessions.

.github/workflows/build-on-pull-request.yml (1)

18-21: Good addition of manual submodule update step

Adding this fallback step ensures that submodules are properly initialized and updated even if the automatic checkout doesn't fully succeed. This provides redundancy and makes the build process more robust.

angular.json (2)

56-62: Enhancement in Production Build Configuration.
The addition of "optimization": true and the new "fileReplacements" array ensures that during production builds the src/environments/environment.ts file is correctly replaced with src/environments/environment.prod.ts. This aligns well with Angular best practices for environment-specific builds and ensures proper configuration for production deployments.


65-70: Streamlining the Development Configuration.
In the development configuration, removal of the "namedChunks" property (with retention of "sourceMap": true) simplifies the build output while still enabling debugging support. Ensure that the removal of named chunks does not affect any downstream tooling that might rely on them.

package.json (4)

14-17: Consistent Prebuild Integration in Build Commands.
Integrating the environment check directly into the build-dev, build-prod, build-ci, and build-test scripts ensures that all build configurations are protected against missing environment files. The additional steps (like chmod +x ./scripts/*.js in the CI build) further enhance reliability.


44-44: New Dependency: ng2-smart-table.
The addition of ng2-smart-table appears intended to enhance table functionalities. Please verify that its version (^1.2.1) is fully compatible with your Angular 16 setup and does not introduce any conflicts with existing libraries.


46-46: New Dependency: node-sass.
node-sass has been added for styling needs. As many projects are transitioning to sass (or dart-sass), please confirm that node-sass is the preferred choice here and that it works seamlessly with the Angular build process, especially given evolving ecosystem trends.


78-78: Updated TypeScript Version Specification.
Changing the TypeScript version specifier from a tilde (~5.1.3) to a caret (^5.1.3) is a good move for accommodating minor version updates. Please ensure that all the related tooling and type definitions are tested against this broader version range.

@Zapper9982
Copy link
Copy Markdown
Contributor Author

Made changes to .eslintrc.json and updated the workflows to now implement npm run build-ci and removed prebuild script

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
.github/workflows/build-on-pull-request.yml (3)

11-17: Review of Checkout Submodules Step

The "Checkout code with submodules" step is now using actions/checkout@v3 with the submodules: true parameter, which correctly enables automatic submodule checkout. However, note that the static analysis tool (actionlint) flags a potential issue with the runner of actions/checkout@v3 being outdated. Please verify whether a newer version (or additional configuration) is recommended by GitHub Actions. Also, line 16 contains trailing spaces that should be removed to conform to YAML formatting guidelines.

🧰 Tools
🪛 actionlint (1.7.4)

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)

[error] 16-16: trailing spaces

(trailing-spaces)


18-21: Review of Manual Submodule Update Step

A new step "Update submodules manually (if needed)" has been added. While explicitly running git submodule init and git submodule update --recursive can serve as a fallback, it might be redundant given that the checkout step already checks out submodules. Please confirm if this redundancy is intentional (perhaps for additional safety) or if the step can be removed to simplify the workflow.


42-42: Review of Build Command Update

The build command is now updated to npm run build-ci. Ensure that the build-ci script is properly defined in your package.json and matches the intended build process. This update seems aligned with the overall goal for a refined CI build, but a quick verification might help avoid unexpected issues during subsequent builds.

.eslintrc.json (1)

35-36: Updated Angular ESLint Rules for TypeScript
Two new rules have been added in the TypeScript overrides:

  • "@angular-eslint/template/click-events-have-key-events": 0 disables the rule to possibly reduce false positives in click event handling.
  • "eqeqeq": 1 sets the loose equality check rule to a warning level rather than enforcing strict equality.

Please verify that having a warning-level for eqeqeq in TypeScript while the JavaScript override enforces strict equality ("error", "always") is intentional. Consistency across the codebase (or a clear rationale for differing levels) may help avoid unintended discrepancies.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8cfb9f8 and efe6fea.

📒 Files selected for processing (3)
  • .eslintrc.json (2 hunks)
  • .github/workflows/build-on-pull-request.yml (2 hunks)
  • package.json (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/build-on-pull-request.yml

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)
.github/workflows/build-on-pull-request.yml

[error] 16-16: trailing spaces

(trailing-spaces)

🔇 Additional comments (5)
.eslintrc.json (5)

8-8: Simplified TypeScript File Pattern
The override now cleanly specifies the files array as ["*.ts"], which improves readability and maintainability.


40-45: Enhanced HTML Override Configuration
The HTML override has been streamlined by condensing the file pattern to a single line (["*.html"]) and extending the configurations to include both accessibility (plugin:@angular-eslint/template/accessibility) and Prettier integration (plugin:prettier/recommended). This approach helps ensure that HTML templates are checked for accessibility and style consistency.


46-53: Prettier Rule for HTML Templates
The rule "prettier/prettier": ["error", { "parser": "angular" }] is added within the HTML override. This configuration enforces formatting standards using Angular’s parser, which should aid in maintaining consistent code style in your templates.


56-69: Strict Linting Settings for JavaScript/JSX
The override for JavaScript and JSX files now includes:

  • A Node environment setup via "env": { "node": true }.
  • Extended base configuration with "eslint:recommended".
  • Parser options adjusted for ECMAScript 2020 and module source type.
  • Rules that enforce a warning for unused variables, disallow console statements, and strictly enforce equality via "eqeqeq": ["error", "always"].

This setup promotes robust linting in JS/JSX files. Ensure that the stricter eqeqeq rule here, compared to the lenient one in the TypeScript configuration, is by design.


1-73: Overall ESLint Configuration Integration
The overall structure shows a coherent strategy for applying specific linting rules based on file types (TypeScript, HTML, JavaScript/JSX). This targeted approach improves the development workflow by ensuring that each file type adheres to the relevant style and consistency standards.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 8, 2025

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (10)
.github/workflows/build-on-pull-request.yml (3)

16-16: Remove Trailing Spaces
There are trailing spaces at the end of the line setting submodules: true. These extra spaces can sometimes lead to YAML parsing issues or style inconsistencies.

-          submodules: true  
+          submodules: true
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 16-16: trailing spaces

(trailing-spaces)


18-21: Verify the Need for Manual Submodule Update
The new step to manually initialize and update submodules might be redundant since the checkout step now automatically includes submodules. Please verify if this extra step is necessary or if it can be removed to simplify the workflow.


23-32: Consider Upgrading Setup Actions for Consistency
The JDK and Node.js setup steps are currently using actions/setup-java@v2 and actions/setup-node@v2. For consistency with other workflows (which have already moved to newer versions) and to benefit from the latest improvements, consider upgrading these to @v4 if possible.

🧰 Tools
🪛 actionlint (1.7.4)

24-24: the runner of "actions/setup-java@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


30-30: the runner of "actions/setup-node@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)

[error] 28-28: trailing spaces

(trailing-spaces)

.github/workflows/package-prod.yml (4)

20-20: Remove Trailing Spaces on Line 20
Trailing spaces can lead to formatting issues. Please remove the extra spaces on line 20.

-      uses: actions/checkout@v4  
+      uses: actions/checkout@v4
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 20-20: trailing spaces

(trailing-spaces)


25-25: Fix Indentation in Java Setup
The static analysis tool indicates a wrong indentation level on line 25 (expected 8 spaces but found 10). Please adjust the indentation in this section for consistency and to avoid YAML parsing warnings.

-          java-version: '17'
+        java-version: '17'
🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 25-25: wrong indentation: expected 8 but found 10

(indentation)


27-28: Remove Trailing Spaces
Trailing spaces are present on lines 27 and 28. Removing these will help maintain consistent formatting.

-          
-  
+          

(Ensure that lines 27 and 28 do not contain any extra spaces)

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 27-27: trailing spaces

(trailing-spaces)


[error] 28-28: trailing spaces

(trailing-spaces)


46-46: Remove Trailing Spaces in Artifact Upload Section
There are trailing spaces at the end of the line in the upload-artifact step. Removing these will ensure cleaner YAML.

-      uses: actions/upload-artifact@v4 
+      uses: actions/upload-artifact@v4
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 46-46: trailing spaces

(trailing-spaces)

.github/workflows/package.yml (3)

18-20: Remove Trailing Spaces on Checkout Step
Static analysis has flagged trailing spaces on line 20. Please remove these extra spaces to adhere to YAML style guidelines.

-      uses: actions/checkout@v4  
+      uses: actions/checkout@v4
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 20-20: trailing spaces

(trailing-spaces)


24-26: Correct Indentation in Java Setup
There is an indentation warning on line 25 (expected 8 spaces but found 10). Please adjust the indentation for consistency with YAML standards.

-      with:
-          java-version: '17'
-          distribution: 'adopt'
+      with:
+        java-version: '17'
+        distribution: 'adopt'
🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 25-25: wrong indentation: expected 8 but found 10

(indentation)


44-46: Remove Trailing Spaces in Artifact Upload
Trailing spaces are detected on line 45. Removing these will clean up the formatting.

-      uses: actions/upload-artifact@v4 
+      uses: actions/upload-artifact@v4
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 45-45: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between efe6fea and 0627883.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (5)
  • .github/workflows/build-on-pull-request.yml (2 hunks)
  • .github/workflows/package-prod.yml (2 hunks)
  • .github/workflows/package.yml (2 hunks)
  • .gitignore (1 hunks)
  • package.json (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .gitignore
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/package-prod.yml

[error] 20-20: trailing spaces

(trailing-spaces)


[warning] 25-25: wrong indentation: expected 8 but found 10

(indentation)


[error] 27-27: trailing spaces

(trailing-spaces)


[error] 28-28: trailing spaces

(trailing-spaces)


[error] 46-46: trailing spaces

(trailing-spaces)

.github/workflows/build-on-pull-request.yml

[error] 16-16: trailing spaces

(trailing-spaces)

.github/workflows/package.yml

[error] 20-20: trailing spaces

(trailing-spaces)


[warning] 25-25: wrong indentation: expected 8 but found 10

(indentation)


[error] 45-45: trailing spaces

(trailing-spaces)

🪛 actionlint (1.7.4)
.github/workflows/build-on-pull-request.yml

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

Comment on lines +11 to +17
- name: Checkout code with submodules
uses: actions/checkout@v3
with:
ref: ${{ github.event.pull_request.head.ref }}
repository: ${{ github.event.pull_request.head.repo.full_name }}
submodules: true

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Update Checkout Action Version
The checkout step is still using actions/checkout@v3. For improved stability and to align with other workflows in the repository, please update this to actions/checkout@v4.

-      - name: Checkout code with submodules
-        uses: actions/checkout@v3
-        with:
-          ref: ${{ github.event.pull_request.head.ref }}
-          repository: ${{ github.event.pull_request.head.repo.full_name }}
-          submodules: true  
+      - name: Checkout code with submodules
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.ref }}
+          repository: ${{ github.event.pull_request.head.repo.full_name }}
+          submodules: true
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout code with submodules
uses: actions/checkout@v3
with:
ref: ${{ github.event.pull_request.head.ref }}
repository: ${{ github.event.pull_request.head.repo.full_name }}
submodules: true
- name: Checkout code with submodules
uses: actions/checkout@v4
with:
ref: ${{ github.event.pull_request.head.ref }}
repository: ${{ github.event.pull_request.head.repo.full_name }}
submodules: true
🧰 Tools
🪛 actionlint (1.7.4)

12-12: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.35.1)

[error] 16-16: trailing spaces

(trailing-spaces)

@drtechie drtechie merged commit e3e7ec1 into PSMRI:develop Apr 9, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[C4GT Community]: Ensure GitHub Actions Pass Successfully with Correct Node Version and Submodules in HWC-Inventory-UI

2 participants