Fix/correct changelog workflow

[pushpitkamboj]

same as title

[openwisp-companion]

Test and Commit Failures

Hello @pushpitkamboj,
(Analysis for commit 4f7d57f)

Test Failure

• Explanation: The Python test test.py failed with a ValueError: Something went terribly wrong on line 10. This indicates an unhandled exception occurred during the test execution.
• Remediation: The provided logs do not contain enough information to determine the exact cause of the ValueError. To fix this, you need to:
  1. Examine the code in test.py around line 10 to understand what operation is causing the error.
  2. If the error is due to incorrect logic in test.py, correct the test assertion or the code it's testing.
  3. If the error is due to an unexpected condition in the code being tested (e.g., file.py), fix the file.py code to handle that condition gracefully or ensure the test case does not trigger it.

Commit Message Failure

• Explanation: The checkcommit tool failed with the error "No capital letter after prefix." This means the commit message does not adhere to OpenWISP's commit message convention, which requires a capitalized short title after the tag.

• Remediation: Ensure your commit message follows this format:

  [tag] Capitalized short title #<issue_number>
  
  Optional detailed description of the changes.
  Must be separated from the header by a blank line.
  
  Fixes #<issue_number>
  

  For example:

  [fix] Corrected an issue with user authentication #123
  
  This commit addresses a bug where users were unable to log in due to an
  incorrectly handled session token.
  
  Fixes #123
  

[openwisp-companion]

Commit Message and Test Failures

Hello @pushpitkamboj,
(Analysis for commit 9ab468f)

Failures & Remediation

1. Commit Message: The checkcommit tool failed because the commit message does not follow the required format. Specifically, it indicates "No capital letter after prefix."

   • Explanation: OpenWISP requires commit messages to start with a tag in square brackets, followed by a capitalized title, and an issue number in the footer. The current commit message violates this by not having a capital letter immediately after the prefix.

   • Remediation: Ensure your commit message follows this format:

     [tag] Capitalized short title #<issue_number>
     
     <Detailed description of changes>
     
     Fixes #<issue_number>
     

     For example:

     [feat] Add new feature X #123
     
     This commit introduces a new feature that allows users to do X.
     It includes changes to the following files: ...
     
     Fixes #123
     

2. Test Failure: A ValueError: Something went terribly wrong occurred during the test execution.

   • Explanation: The traceback indicates an uncaught ValueError originating from test.py on line 10. This suggests an issue within the test or the code being tested that leads to this specific exception.
   • Remediation: Examine the test.py file and the code it interacts with to identify the cause of the ValueError. Based on the provided logs, the error occurs in test.py on line 10. You need to debug this section to either fix the underlying logic that raises the ValueError or adjust the test to handle expected exceptions if that is the intended behavior. Since the specific code causing the ValueError is not shown, a precise code fix cannot be provided. However, the error message "Something went terribly wrong" is generic and points to a logic error.