take-action
This is an action to assign yourself to an issue for a repo you are not a contributor to. (by bdougie)
naming-cheatsheet
Comprehensive language-agnostic guidelines on variables naming. Home of the A/HC/LC pattern. (by kettanaito)
| take-action | naming-cheatsheet | |
|---|---|---|
| 5 | 24 | |
| 50 | 13,657 | |
| - | - | |
| 2.7 | 0.6 | |
| 30 days ago | 2 months ago | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
take-action
Posts with mentions or reviews of take-action.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-31.
-
GitHub Actions: A Maintainer's Best Friend
My coworker bdougie (@bdougieyo) created the take Github action. It allows external contributors to self-assign issues by typing .take into a comment of an issue. This removes the burden of a bit of back and forth between contributors and maintainers.
-
How to Edit a Github Action
You can find my PR here. In this PR, I made a pull request comparing my branch to the author’s branch.
-
Build your own GitHub Action WITHOUT a Docker Container
I recently moved my bdougie/take-action to run out of the yml and not look back. Here is that PR.
-
Build GitHub Actions with a Docker Container
And now you can push this to GitHub to test it from a repo. I leverage this actual action in my repo bdougie/take-action got a response back from my action, it looks like it worked okay.
-
Assigning new contributors to issues using GitHub Actions
bdougie / take-action
naming-cheatsheet
Posts with mentions or reviews of naming-cheatsheet.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-07.
-
My team lead always fails my code
This guide is my go-to recommendation for freshers for "naming things": https://github.com/kettanaito/naming-cheatsheet
- Clean code (la juniori)
-
Some scripts work weirdly
Use better naming. What's variablename? var iab; len(name)? What does reader do? Read a book? https://github.com/kettanaito/naming-cheatsheet
-
Help with this password generator
Not an answer, but https://github.com/kettanaito/naming-cheatsheet
-
Variable inside a function with the same name?
But why would you need variable inside a function with the same name? https://github.com/kettanaito/naming-cheatsheet
-
Live coding preparation tips
Use the programming language you're most comfortable with if requirements are not strictly coupled to one programming language. Share your thoughts while you're coding so the interviewers can feel your way of thinking and problem-solving. Also, ask questions when something needs to be clarified for you. Try not to write pieces of code you don't fully understand, for example, using IIFE and not knowing how to pass an argument into it, using ; in front of it, and not knowing why it's used. Try to write readable code with understandable variable and function names. Avoid writing too nested statements, so it's not easy to understand the code's flow. Try to write code that is easy to cover with the tests.
- What are some things you look for during a code review?
-
Great resources for learning React and Typescript
Naming Convention Cheatsheet
-
How to cope with varying writing styles in code docs and logging messages?
Enforce style with a linter. In the js world there is also prettier. Agree upon a naming style for instance this naming cheatsheet although that is harder to enforce
-
What does it take to be a good programmer?
What a great answer :)
Regarding naming things, this comes to my mind: https://github.com/kettanaito/naming-cheatsheet
What are some alternatives?
When comparing take-action and naming-cheatsheet you can also consider the following projects:
github-script - Write workflows scripting the GitHub API in JavaScript
visx - 🐯 visx | visualization components
redux-ecosystem-links - A categorized list of Redux-related addons, libraries, and utilities
naming-convention - Templates for naming convention - TSQL, JavaScript, C#, R, Python, Powershell
app - 🍕 Insights into your entire open source ecosystem.
Front-End-Checklist - 🗂 The perfect Front-End Checklist for modern websites and meticulous developers
nissuer - A GitHub Action for tried and tired maintainers.
modern-php-cheatsheet - Cheatsheet for some PHP knowledge you will frequently encounter in modern projects.
deploy-with-actions
markdown-wikitext - A cheatsheet mirroring Markdown and Wikitext
www.nickyt.co - Source code for my web site nickyt.co
scaffdog - :dog: scaffdog is Markdown driven scaffolding tool.
take-action vs github-script
naming-cheatsheet vs visx
take-action vs redux-ecosystem-links
naming-cheatsheet vs naming-convention
take-action vs app
naming-cheatsheet vs Front-End-Checklist
take-action vs nissuer
naming-cheatsheet vs modern-php-cheatsheet
take-action vs deploy-with-actions
naming-cheatsheet vs markdown-wikitext
take-action vs www.nickyt.co
naming-cheatsheet vs scaffdog