docs: add conditional deployment use case to readme

[tprouvot]

What does this pull request contain?

Add conditional deplyment use case in the README, as a solution to solve deployment errors when delta files are empty.

Does this close any currently open issues?

closes #249

[scolladon]

LGTM

Thanks for this addition

[codecov]

Codecov Report

Merging #289 (13480a7) into main (f43b8e0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #289   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          628       628           
=========================================
  Hits           628       628           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f43b8e0...13480a7. Read the comment docs.

[scolladon]

Few changes we can discuss.

Thanks for the work so far, I think it is very helpful

[mehdicherf]

Thank you Thomas!
In addition to @scolladon comments, I would add 2 things:

1. Add the new section to the Table of Contents
2. I would put it before the U_se the module in your own node application_ section (that last section is for very specific use-cases, and should remain at the bottom, IMO).

[scolladon]

Thank you Thomas!

In addition to @scolladon comments, I would add 2 things:

1. Add the new section to the Table of Contents

2. I would put it before the U_se the module in your own node application_ section (that last section is for very specific use-cases, and should remain at the bottom, IMO).

@tprouvot I can help on the Table of Content generation, we use a tool to do that automatically, give me access to your repo and I'll contribute

[codeclimate]

Code Climate has analyzed commit 13480a7 and detected 0 issues on this pull request.

View more on Code Climate.

[mehdicherf]

LGTM.

Thank you Thomas!

[scolladon]

LGTM

[tprouvot]

Thank you Thomas!
In addition to @scolladon comments, I would add 2 things:

1. Add the new section to the Table of Contents
2. I would put it before the U_se the module in your own node application_ section (that last section is for very specific use-cases, and should remain at the bottom, IMO).

@tprouvot I can help on the Table of Content generation, we use a tool to do that automatically, give me access to your repo and I'll contribute

Hi @scolladon I should have accepted your proposition because I tested the table of content on the new entry and it doesn't redirect to the section... I found the issue on the link and fixed it on my repo. Would you like me to create another PR ?

tprouvot@80f980f

[scolladon]

@tprouvot that's a good idea, yes please create another PR (fix type)