Skip to content

Conversation

@OluwatobiOni
Copy link
Collaborator

Created a function to uplift costs at extract stage. Applied the uplift to relevant recids (00B, 01B, 02B, 04B, AE2).

@OluwatobiOni OluwatobiOni self-assigned this Sep 23, 2025
@OluwatobiOni
Copy link
Collaborator Author

OluwatobiOni commented Sep 23, 2025

Hi Zihao, I have reviewed the feedback and re-wrote the code to avoid duplication as much as possible. @lizihao-anu

Copy link
Collaborator

@lizihao-anu lizihao-anu left a comment

Choose a reason for hiding this comment

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

I have tested and the code looks great!

OluwatobiOni and others added 3 commits September 23, 2025 16:53
Although the checks passed, I noticed the document.yaml workflow was failing on the smr-cost-uplift branch. It looks like this issue is also present in the master and dec25-update branches when I checked the document workflow in the actions tab for those branches too.

I inspected the error and it was a git push rejection. This happened because the workflow's automated git-auto-commit-action tried to push documentation updates, but the remote branch on GitHub already had newer commits. 

To fix this, I've committed a change to the document.yaml workflow. The solution was to add a step to git pull the latest changes from the remote branch before the auto-commit action runs. This ensures the workflow is always working on the most up-to-date version of the branch and can push its changes without conflict.

The workflow should now run and pass correctly. Let me know if you have any questions.
Reverting changes as it failed because of an overall changed workflow
@OluwatobiOni OluwatobiOni merged commit 628265b into dec25-update Sep 23, 2025
4 checks passed
@OluwatobiOni OluwatobiOni deleted the smr-cost-uplift branch September 23, 2025 16:26
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.

3 participants