Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge episode 2 and 3 #18

Merged
merged 4 commits into from
Oct 28, 2024
Merged

merge episode 2 and 3 #18

merged 4 commits into from
Oct 28, 2024

Conversation

gcroci2
Copy link
Collaborator

@gcroci2 gcroci2 commented Oct 26, 2024

No description provided.

@gcroci2 gcroci2 linked an issue Oct 26, 2024 that may be closed by this pull request
Copy link

github-actions bot commented Oct 26, 2024

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/olgaminaeva/gen-ai-coding/compare/md-outputs..md-outputs-PR-18

The following changes were observed in the rendered markdown documents:

 ...ion-ai-coding.md => 1-introduction-ai-coding.md |   0
 ...ization.md => 2-code-generation-optimization.md | 364 ++++++++++++++++++---
 ....md => 3-ethical-and-security-considerations.md |   0
 config.yaml                                        |   7 +-
 enhancing-coding-efficiency.md (gone)              | 250 --------------
 md5sum.txt                                         |   9 +-
 6 files changed, 319 insertions(+), 311 deletions(-)
What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-10-27 14:26:39 +0000

github-actions bot pushed a commit that referenced this pull request Oct 26, 2024
github-actions bot pushed a commit that referenced this pull request Oct 26, 2024
github-actions bot pushed a commit that referenced this pull request Oct 26, 2024
github-actions bot pushed a commit that referenced this pull request Oct 27, 2024
@olgaminaeva olgaminaeva merged commit 6f167f3 into main Oct 28, 2024
3 checks passed
github-actions bot pushed a commit that referenced this pull request Oct 28, 2024
Auto-generated via `{sandpaper}`
Source  : 6f167f3
Branch  : main
Author  : Olga Minaeva <[email protected]>
Time    : 2024-10-28 11:09:48 +0000
Message : Merge pull request #18 from olgaminaeva/merge_2_3_gcroci2

merge episode 2 and 3
github-actions bot pushed a commit that referenced this pull request Oct 28, 2024
Auto-generated via `{sandpaper}`
Source  : a747bc7
Branch  : md-outputs
Author  : GitHub Actions <[email protected]>
Time    : 2024-10-28 11:10:38 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 6f167f3
Branch  : main
Author  : Olga Minaeva <[email protected]>
Time    : 2024-10-28 11:09:48 +0000
Message : Merge pull request #18 from olgaminaeva/merge_2_3_gcroci2

merge episode 2 and 3
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.

Merge together episodes 2 and 3
2 participants