hey team! this is a small thing, but it would be nice if the platform looked for a render.yml
file in addition to render.yaml
.
I think it’s dumb, but rails doesn’t look for, for instance, database.yaml
:
it’s not such a big deal for a solo dev to have *.yml
in the rails project with a single render.yaml
file in the root, but for larger teams / projects it can lead to annoying problems, and plus, consistencyyyy
just want to add, supporting .yml
isn’t without precedent. ansible
seems to use .yml
consistently:
# test code for the git module
# (c) 2014, James Tanner <tanner.jc@gmail.com>
# This file is part of Ansible
#
# Ansible is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Ansible is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Ansible. If not, see <http://www.gnu.org/licenses/>.
- import_tasks: setup.yml
- import_tasks: setup-local-repos.yml
This file has been truncated. show original
and it seems as though GitHub actions only supported .yml
until fairly recently:
I know this is minutae, but I’m wondering if anyone could shed some light on the reasoning for picking and only supporting .yml over .yaml? I see this happening in various projects, but it runs counter to yaml’s own...
Reading time: 1 mins 🕑
Likes: 8 ❤
(their documentation now lists both as being valid)
This is a great suggestion! I’ve added a feature request at Support for render.yml | Feature Requests | Render .
I suggest you upvote and we can get it into our product roadmap.