TEST - DO NOT APPROVE #418
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix missing FromQuery params Fix integration tests not using JSON datasource mocker
I, Margaret <[email protected]>, hereby add my Signed-off-by to this commit: f881406 I, Margaret <[email protected]>, hereby add my Signed-off-by to this commit: f343cab Signed-off-by: Margaret <[email protected]>
Signed-off-by: Yasumasa Suenaga <[email protected]>
* cleaning workflows Signed-off-by: Dan Benitah <[email protected]> * pull request should on trigger for pull request event - removing on push for PRs Signed-off-by: Dan Benitah <[email protected]> * syntax Signed-off-by: Dan Benitah <[email protected]> * syntax Signed-off-by: Dan Benitah <[email protected]> * moving markdown linting and disabling 2.a-deploy Signed-off-by: Dan Benitah <[email protected]> * adding some jobs dependencies so packaging does not run if code does not build etc... Signed-off-by: Dan Benitah <[email protected]> * moving code analysis into the build step and clean up Signed-off-by: Dan Benitah <[email protected]> --------- Signed-off-by: Dan Benitah <[email protected]> Co-authored-by: danuw <[email protected]>
* Skip deploy workflows in forked repos Signed-off-by: Yasumasa Suenaga <[email protected]> * Add vars Signed-off-by: Yasumasa Suenaga <[email protected]> --------- Signed-off-by: Yasumasa Suenaga <[email protected]>
Signed-off-by: Roman Lutz <[email protected]>
…rbon-aware-sdk into romanlutz/fix_typos
Fix typos in packaging doc
Issue : I have tested a ElectricityMaps forecast scenario CLI: "emissions-forecasts -l westeurope -v" will return server error 500. Analysis: public async Task<EmissionsForecast> GetCurrentCarbonIntensityForecastAsync(Location location) is causing the EM server to return 500. Reason is that the "." in geolocation.Latitude will be passed as "," Fix: The following changes are fixing this bug. Signed-off-by: Christian Binder <[email protected]>
Signed-off-by: Yasumasa Suenaga <[email protected]>
fixing 3 broken links in overview.md Signed-off-by: nttDamien <[email protected]>
Integration tests coverage for WebAPI and CLI
Signed-off-by: Roman Lutz <[email protected]>
Signed-off-by: Szymon Duchniewicz <[email protected]>
Fix: verify-azure-function-with-packages #383
…receives request for forecast Signed-off-by: Yasumasa Suenaga <[email protected]>
EMFree data source should regard specified time range
24 tasks
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #418 +/- ##
==========================================
+ Coverage 74.21% 74.67% +0.46%
==========================================
Files 77 77
Lines 2637 2646 +9
Branches 266 268 +2
==========================================
+ Hits 1957 1976 +19
+ Misses 598 589 -9
+ Partials 82 81 -1
|
24 tasks
25 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR)
something else
copilot:description
Summary (summary)
copilot:summary
Changes (walkthrough)
copilot:walkthrough
copilot:poem
Checklist
Are there API Changes?
If yes, what are the expected API Changes? Please link to an API-Comparison
workflow with the API Diff.
Is this a breaking change?
If yes, what workflow does this break?
Anything else?
Other comments, collaborators, etc.
This PR Closes #<issue_number>