Skip to content

Add solution for Challenge 18 by alimkinpark#1639

Open
alimkinpark wants to merge 1 commit into
RezaSi:mainfrom
alimkinpark:challenge-18-alimkinpark
Open

Add solution for Challenge 18 by alimkinpark#1639
alimkinpark wants to merge 1 commit into
RezaSi:mainfrom
alimkinpark:challenge-18-alimkinpark

Conversation

@alimkinpark
Copy link
Copy Markdown
Contributor

Challenge 18 Solution

Submitted by: @alimkinpark
Challenge: Challenge 18

Description

This PR contains my solution for Challenge 18.

Changes

  • Added solution file to challenge-18/submissions/alimkinpark/solution-template.go

Testing

  • Solution passes all test cases
  • Code follows Go best practices

Thank you for reviewing my submission! 🚀

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 30, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a498a064-9b07-452f-b3bd-8635b72c0abe

📥 Commits

Reviewing files that changed from the base of the PR and between bf844ae and 325f138.

📒 Files selected for processing (1)
  • challenge-18/submissions/alimkinpark/solution-template.go

Walkthrough

A new Go executable file is added that implements temperature conversion functions for converting between Celsius and Fahrenheit using standard formulas. The program includes helper logic for rounding results to two decimal places and demonstrates example conversions with formatted output.

Changes

Cohort / File(s) Summary
Challenge 18 Solution
challenge-18/submissions/alimkinpark/solution-template.go
New Go program introducing CelsiusToFahrenheit(), FahrenheitToCelsius(), and Round() functions to convert temperatures with decimal precision, plus a main() function demonstrating example conversions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Poem

🐰 Hop along with Celsius and Fahrenheit cheer,
A rabbit converts temps throughout the year,
With math.Round and formulas precise,
Twenty-five becomes sixty-eight—quite nice! ❄️🔥

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: adding a solution for Challenge 18 by a specific contributor.
Description check ✅ Passed The description is directly related to the changeset, explaining the Challenge 18 solution submission and the added file.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.4)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

⚠️ Auto-merge failed

Could not automatically merge this PR: Resource not accessible by integration

A maintainer will need to merge manually.

1 similar comment
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

⚠️ Auto-merge failed

Could not automatically merge this PR: Resource not accessible by integration

A maintainer will need to merge manually.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

👋 Action needed for auto-merge

This PR cannot be auto-merged because "Allow edits from maintainers" is enabled. This is a GitHub limitation with automated workflows.

To fix: Please uncheck "Allow edits from maintainers" in the PR sidebar (under the reviewers section), and the PR will be auto-merged in the next cycle.

Alternatively, a maintainer can merge this manually.

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.

1 participant