Add :robot: for files generated or updated automatically with a script
See original GitHub issueHello @carloscuesta 😎!
- Emoji: 🤖
- Code:
:robot:
- Description:
- I have seen workflows where a lot of files need to be auto-generated using custom scripts.
- For instance, at my workplace we use a script to generate React Icon Components from SVG files.
- In such situations where the change was auto-generated, this emoji would be extremely helpful to display a script- generated change.
- An example commit might look like so:
- 🤖 Auto-generate icon component for new plus icon
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Adding script automation to a robot - HighBond
If you previously created the robot, you need to open the robot and navigate to the script editor. Open the Robots app.
Read more >How to automatically add a newly created header file to new ...
In Robot, click File->Open an SQABasic File. · In Files of type, select Template Files (*.tpl). · Select testproc.tpl, and then click Open....
Read more >Create and submit a robots.txt file | Google Search Central
A robots.txt file lives at the root of your site. Learn how to create a robots.txt file, see examples, and explore robots.txt rules....
Read more >How to Automate Your Work with an Office Script Bot - YouTube
By using Power Automate we can allow Gmail and office script to ... code from the current sub: F5 Step into the code...
Read more >How to load a Script file - RoboDK Documentation
The following steps and images summarize the procedure to execute a SCRIPT program on the robot. These steps are not required to run...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the idea for this gitmoji is to be used within CIs or bots that automatically generate commits and push them to a repository.
Let’s say that for example, you have a workflow that once you publish a release, a changelog file is generated from a GitHub Action and the changes are published into the master branch.
I understand the reason why you thought about this! However, instead what I would do is trying to categorise the commits that the script is doing using the proper gitmoji, for example:
Why instead of using the 🤖 that is actually indicating that the commit was made from an automation we don’t use 🍱which is the emoji for indicating that some assets were updated?
In my opinion, this approach is better as you’re expressing the intention of the commit, no matter who the author is 😊
I really think that 🤖 is quite appropriate for script-generated changes, since package doesn’t adequately convey the message.
If understanding the change requires reading the description of the emoji, then that defeats the purpose altogether, right?
Yet, I think that you surely know better and if you think that we shouldn’t go ahead with this, then I’ll just go ahead and close the issue.