{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":808597527,"defaultBranch":"main","name":"copy","ownerLogin":"psergee","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-05-31T11:59:11.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/76554065?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1717156758.463922","currentOid":""},"activityList":{"items":[{"before":"ece07202ab6562f6aebad51bae8459c639aed62a","after":"1ddce651c8095269210a10836a52f47748e68a98","ref":"refs/heads/main","pushedAt":"2024-06-06T14:07:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"Fix relative symlinks copying\n\nAll relative paths of symbolic links should be resolved from the\ndirectory where the link is located. The current working directory\ndoes not affect the resolution of the path. A symbolic link can\nbe absolute or relative, and may or may not have a leading dot.\nDirectory content example:\nfile\nsymlink -> file\nCopying of the directory with such content does not work currently.\nWhen copying `symlink`, `Copy` returns an error because the `file`\ndoes not exist in the current working directory. In the existing\ntests, there is a symbolic link named \"symlink\" that points to a\nfile named \"README.md\". However, when resolving the path of the\nfile, the file is located in the repository's root directory,\nnot the test case directory, and copying of these dirs work fine.\n\nThe solution is to check whether the resolved path is absolute\nor not. If it is not, append it to the file's directory path.","shortMessageHtmlLink":"Fix relative symlinks copying"}},{"before":"46409a573c8607c695ee0aadc06e8224704a1bf1","after":"ece07202ab6562f6aebad51bae8459c639aed62a","ref":"refs/heads/main","pushedAt":"2024-06-01T14:07:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"Fix relative symlinks copying\n\nAll relative paths of symbolic links should be resolved from the\ndirectory where the link is located. The current working directory\ndoes not affect the resolution of the path. A symbolic link can\nbe absolute or relative, and may or may not have a leading dot.\nDirectory content example:\nfile\nsymlink -> file\nCopying of the directory with such content does not work currently.\nWhen copying `symlink`, `Copy` returns an error because the `file`\ndoes not exist in the current working directory. In the existing\ntests, there is a symbolic link named \"symlink\" that points to a\nfile named \"README.md\". However, when resolving the path of the\nfile, the file is located in the repository's root directory,\nnot the test case directory, and copying of these dirs work fine.\n\nThe solution is to check whether the resolved path is absolute\nor not. If it is not, append it to the file's directory path.","shortMessageHtmlLink":"Fix relative symlinks copying"}},{"before":"21d857c54e2343a539622756cb0780d028bd2863","after":"46409a573c8607c695ee0aadc06e8224704a1bf1","ref":"refs/heads/main","pushedAt":"2024-06-01T13:49:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"Fix relative symlinks copying\n\nAll relative paths of symbolic links should be resolved from the\ndirectory where the link is located. The current working directory\ndoes not affect the resolution of the path. A symbolic link can\nbe absolute or relative, and may or may not have a leading dot.\nDirectory content example:\nfile\nsymlink -> file\nCopying of the directory with such content does not work currently.\nWhen copying `symlink`, `Copy` returns an error because the `file`\ndoes not exist in the current working directory. In the existing\ntests, there is a symbolic link named \"symlink\" that points to a\nfile named \"README.md\". However, when resolving the path of the\nfile, the file is located in the repository's root directory,\nnot the test case directory, and copying of these dirs work fine.\n\nThe solution is to check whether the resolved path is absolute\nor not. If it is not, append it to the file's directory path.","shortMessageHtmlLink":"Fix relative symlinks copying"}},{"before":"bb3da59962e3a8fa886e6840f6f70d3d39ea3a02","after":"21d857c54e2343a539622756cb0780d028bd2863","ref":"refs/heads/main","pushedAt":"2024-06-01T13:10:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"Fix relative symlinks copying\n\nAll relative paths of symbolic links should be resolved from the\ndirectory where the link is located. The current working directory\ndoes not affect the resolution of the path. A symbolic link can\nbe absolute or relative, and may or may not have a leading dot.\nDirectory content example:\nfile\nsymlink -> file\nCopying of the directory with such content does not work currently.\nWhen copying `symlink`, `Copy` returns an error because the `file`\ndoes not exist in the current working directory. In the existing\ntests, there is a symbolic link named \"symlink\" that points to a\nfile named \"README.md\". However, when resolving the path of the\nfile, the file is located in the repository's root directory,\nnot the test case directory, and copying of these dirs work fine.","shortMessageHtmlLink":"Fix relative symlinks copying"}},{"before":"0222227c114e3b1e7d51c226f34d8ca067068ca1","after":"bb3da59962e3a8fa886e6840f6f70d3d39ea3a02","ref":"refs/heads/main","pushedAt":"2024-05-31T14:39:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"change mod path","shortMessageHtmlLink":"change mod path"}},{"before":"c464078e5ed4b740a74d31e7c6ff97868c863ffe","after":"0222227c114e3b1e7d51c226f34d8ca067068ca1","ref":"refs/heads/main","pushedAt":"2024-05-31T14:35:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"psergee","name":"Pavel Sergeev","path":"/psergee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/76554065?s=80&v=4"},"commit":{"message":"Fix relative symlinks copying\n\nAll relative paths of symbolic links should be resolved from the\ndirectory where the link is located. The current working directory\ndoes not affect the resolution of the path. A symbolic link can\nbe absolute or relative, and may or may not have a leading dot.\nDirectory content example:\nfile\nsymlink -> file\nCopying of the diectory with such content does not work currently.\nWhen copying `symlink`, `Copy` returns an error because the `file`\ndoes not exist in the current working directory. In the existing\ntests, there is a symbolic link named \"symlink\" that points to a\nfile named \"README.md\". However, when resolving the path of the\nfile, the file is located in the repository's root directory,\nnot the case* directory. So the tests work fine.","shortMessageHtmlLink":"Fix relative symlinks copying"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNi0wNlQxNDowNzoyOS4wMDAwMDBazwAAAAReRMCb","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNi0wNlQxNDowNzoyOS4wMDAwMDBazwAAAAReRMCb","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNS0zMVQxNDozNTo1NS4wMDAwMDBazwAAAARZHuCZ"}},"title":"Activity · psergee/copy"}