This simplifies the creation of dataframe to html and creates a self.df object in table builder that can be called across different business rules with the required data
It is worth noting here the "current_runs_build" and "done_runs_build" methods can probably be simplified but I'm of two minds here on that as I don't think it improves readability as the two sql concepts are actually quite different and the inverse of eachother
Also keep an eye on the "left Join" in current runs build, this could become quite slow as the data grows... but seriously this is on my little thing I doubt it will ever be a problem
This simplifies the creation of dataframe to html and creates a self.df object in table builder that can be called across different business rules with the required data
It is worth noting here the "current_runs_build" and "done_runs_build" methods can probably be simplified but I'm of two minds here on that as I don't think it improves readability as the two sql concepts are actually quite different and the inverse of eachother
Also keep an eye on the "left Join" in current runs build, this could become quite slow as the data grows... but seriously this is on my little thing I doubt it will ever be a problem
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This simplifies the creation of dataframe to html and creates a self.df object in table builder that can be called across different business rules with the required data
It is worth noting here the "current_runs_build" and "done_runs_build" methods can probably be simplified but I'm of two minds here on that as I don't think it improves readability as the two sql concepts are actually quite different and the inverse of eachother
Also keep an eye on the "left Join" in current runs build, this could become quite slow as the data grows... but seriously this is on my little thing I doubt it will ever be a problem