Why dotenv files should be listed in reverse order to get expected result?

[vudaltsov]

# .env
A=1

# .env.local
A=2

# Taskfile.yml
version: '3'

dotenv:
  - '.env'
  - '.env.local'

tasks:
  test: echo {{.A}}

task test outputs 1 instead of 2. Isn't it counterintuitive that env variables from subsequent files do not override the ones from preceding? For instance, shell itself outputs 2 for source .env && source .env.local && echo "$A".

[barrykaplan]

Ha! I just ran into this. I have .env and .env.secret (ignored). So I have a task that copies the keys from .env.secret to .env to document what is expected locally. So like

# .env
E1=e1
E2=e2

# expected in .env.secret
S1=""
S2=""

I expected dotenv files to be loaded in order, so of course that caused a problem. I changed the task to sync the secret env's as comments. Probably a better in any case, but still the ordering by task is counter intuitive.