You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that 178 out of 381 issues in the issues/ folder have an empty revert_command.txt and instead have an issue_introduction.patch.
Do these patches reflect actual historical states of the Expensify repo, or were they created post hoc? The paper mentions doing something similar in Appendix A.11, but I think only for the held out set?
Could you clarify what's different between issues that have an issue_introduction.patch and issues that don't?
The text was updated successfully, but these errors were encountered:
I noticed that 178 out of 381 issues in the
issues/
folder have an emptyrevert_command.txt
and instead have anissue_introduction.patch
.Do these patches reflect actual historical states of the Expensify repo, or were they created post hoc? The paper mentions doing something similar in Appendix A.11, but I think only for the held out set?
Could you clarify what's different between issues that have an
issue_introduction.patch
and issues that don't?The text was updated successfully, but these errors were encountered: