Presently proposalID (directory from where the data are taken) is inserted in the every pyzebra panel separately, and should be re-inserted when pyzebra is reloaded. We would like to have the proposalID shared by all panels and kept by pyzebra also when it is reloaded.
*Created by: zaharko*
Presently proposalID (directory from where the data are taken) is inserted in the every pyzebra panel separately, and should be re-inserted when pyzebra is reloaded. We would like to have the proposalID shared by all panels and kept by pyzebra also when it is reloaded.
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.
Created by: zaharko
Presently proposalID (directory from where the data are taken) is inserted in the every pyzebra panel separately, and should be re-inserted when pyzebra is reloaded. We would like to have the proposalID shared by all panels and kept by pyzebra also when it is reloaded.