It is a convention for projects using python.&nbsp; It definitely isn't required but there are some features that come for free when using that filename.&nbsp;<br /><br /><a href="https://github.blog/2018-07-12-security-vulnerability-alerts-for-python/">https://github.blog/2018-07-12-security-vulnerability-alerts-for-python/</a><br />and&nbsp;<br /><a href="https://help.github.com/en/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on">https://help.github.com/en/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on</a><br /><br />You can also get more insight from github into dependencies and dependents.&nbsp;&nbsp;<br />example: <a href="https://github.com/tianocore/edk2-pytool-extensions/network/dependencies">https://github.com/tianocore/edk2-pytool-extensions/network/dependencies</a><br /><br />I did notice on the example from above that github picked up the requirements.publisher.txt so i don't know what their pattern matching does exactly.<br /><br /><br /><br />