Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Should I post a link to the Github repo for code reviews?

Parent

Should I post a link to the Github repo for code reviews?

+6
−0

Hello. Total noob here and noob to this site. I've written a non-trivial program in Python. Code review didn't take the whole thing (400+ lines of code). Should I post a link to my Github repo or is that not appropriate?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+1
−4

Total noob here and noob to this site. I've written a non-trivial program in Python.

I'm the only one who see contradiction here? Anyway, posting link to GitHub repo is absolutely appropriate. Moreover I'd say this is the best way for something that is more than 100 lines of code.

One can write an answer with explanations and also open PR with suggestions. You don't have to merge it but I believe it would be easier for you to understand feedback this way. At least that's how I usually do code-review from communities like this one when link to github repo is available.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

I think he means he's a noob of the site, not a noob of Python. (2 comments)
I think he means he's a noob of the site, not a noob of Python.
matthewsnyder‭ wrote over 1 year ago

I think he means he's a noob of the site, not a noob of Python.

FoggyFinder‭ wrote over 1 year ago

matthewsnyder‭ there is clear "and"