url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://www.youtube.com/@EverythingOpen | Everything Open - YouTube var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"GFEEDBACK","params":[{"key":"route","value":"channel."},{"key":"is_owner","value":"false"},{"key":"is_alc_surface","value":"false"},{"key":"browse_id","value":"UCdEnOgR3rcYfIpzdAc8QsRQ"},{"key":"browse_id_prefix","value":""},{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgttRS1udmllOW5LbyiFoZjLBjIKCgJLUhIEGgAgXQ%3D%3D"}]},{"service":"GOOGLE_HELP","params":[{"key":"browse_id","value":"UCdEnOgR3rcYfIpzdAc8QsRQ"},{"key":"browse_id_prefix","value":""}]},{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetChannelPage_rid","value":"0x6d917d96e463a35f"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"maxAgeSeconds":300,"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRT2-ow50eEJRbMWc5wtQg8IqpAdjm8jm3YBwRgkuswmIBwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["pageHeaderRenderer","pageHeaderViewModel","imageBannerViewModel","dynamicTextViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","flexibleActionsViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","descriptionPreviewViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sectionListRenderer","itemSectionRenderer","continuationItemRenderer","attributionViewModel","channelMetadataRenderer","twoColumnBrowseResultsRenderer","tabRenderer","shelfRenderer","horizontalListRenderer","gridVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayToggleButtonRenderer","thumbnailOverlayNowPlayingRenderer","menuRenderer","menuServiceItemRenderer","menuNavigationItemRenderer","unifiedSharePanelRenderer","expandableTabRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgttRS1udmllOW5LbyiFoZjLBjIKCgJLUhIEGgAgXQ%3D%3D","rootVisualElementType":3611},"hasDecorated":true}},"contents":{"twoColumnBrowseResultsRenderer":{"tabs":[{"tabRenderer":{"endpoint":{"clickTrackingParams":"CCQQ8JMBGAUiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen/featured","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","params":"EghmZWF0dXJlZPIGBAoCMgA%3D","canonicalBaseUrl":"/@EverythingOpen"}},"title":"홈","selected":true,"content":{"sectionListRenderer":{"contents":[{"itemSectionRenderer":{"contents":[{"shelfRenderer":{"title":{"runs":[{"text":"Everything Open 2025","navigationEndpoint":{"clickTrackingParams":"CJACENwcGAAiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLI3yu3oBYCpj5bsSbk0aPbtL4yE4V1F_8","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLI3yu3oBYCpj5bsSbk0aPbtL4yE4V1F_8"}}}]},"endpoint":{"clickTrackingParams":"CJACENwcGAAiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLI3yu3oBYCpj5bsSbk0aPbtL4yE4V1F_8","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLI3yu3oBYCpj5bsSbk0aPbtL4yE4V1F_8"}},"content":{"horizontalListRenderer":{"items":[{"gridVideoRenderer":{"videoId":"gIoNqxAXfG4","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/gIoNqxAXfG4/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhyIEwoQTAP\u0026rs=AOn4CLD6Cr-rR4FrAc7frq61eg8Uh1lU4g","width":168,"height":94},{"url":"https://i.ytimg.com/vi/gIoNqxAXfG4/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhyIEwoQTAP\u0026rs=AOn4CLADIlfu95Hj7gqwwdc8fs6axuYj1Q","width":196,"height":110},{"url":"https://i.ytimg.com/vi/gIoNqxAXfG4/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYciBMKEEwDw==\u0026rs=AOn4CLCv1KbXvevpPqE7jTjkdLGBsW0Jmw","width":246,"height":138},{"url":"https://i.ytimg.com/vi/gIoNqxAXfG4/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYciBMKEEwDw==\u0026rs=AOn4CLDam5BIexElJuB9tMmg96CV_JKB5g","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Cargo Cult Standards Compliance: Proprietary Standards in an Open Source World - Bishop (EO2025) 42분"}},"simpleText":"Cargo Cult Standards Compliance: Proprietary Standards in an Open Source World - Bishop (EO2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 38회"},"navigationEndpoint":{"clickTrackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=gIoNqxAXfG4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"gIoNqxAXfG4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=808a0dab10177c6e\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiFA7vjdgLG1g8WAAaoBIlBMSTN5dTNvQllDcGo1YnNTYmswYVBidEw0eUU0VjFGXzg=","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 38회"}},"simpleText":"조회수 38회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CNwCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNwCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"gIoNqxAXfG4","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CNwCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["gIoNqxAXfG4"],"params":"CAQ%3D"}},"videoIds":["gIoNqxAXfG4"],"videoCommand":{"clickTrackingParams":"CNwCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=gIoNqxAXfG4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"gIoNqxAXfG4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=808a0dab10177c6e\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CNwCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CNsCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNsCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtnSW9OcXhBWGZHNA%3D%3D"}}}}}},"trackingParams":"CNsCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtnSW9OcXhBWGZHNA%3D%3D","commands":[{"clickTrackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CNoCEI5iIhMIqqfUjJqIkgMVYbZWAR3jHyIh","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","hasSeparator":true}}],"trackingParams":"CNcCEJQ1GAAiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"42분 7초"}},"simpleText":"42:07"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CNkCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"gIoNqxAXfG4","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CNkCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"gIoNqxAXfG4"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CNkCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CNgCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNgCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"gIoNqxAXfG4","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CNgCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["gIoNqxAXfG4"],"params":"CAQ%3D"}},"videoIds":["gIoNqxAXfG4"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CNgCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"WwLSPc01A6E","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/WwLSPc01A6E/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLDHU-M-_JxvWCM_bS66Q5kihk1dLA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/WwLSPc01A6E/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLC_T_0fU6gC_Que1V6XYI139-u69A","width":196,"height":110},{"url":"https://i.ytimg.com/vi/WwLSPc01A6E/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLA55JB5WdS5fcVF0Av-hRUK0MxrSA","width":246,"height":138},{"url":"https://i.ytimg.com/vi/WwLSPc01A6E/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLCgAKt82w60taARUanHCsWz4kB6Xg","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"All the wonderful things you can do with StackRox - Shane Boulden (Everything Open 2025) 28분"}},"simpleText":"All the wonderful things you can do with StackRox - Shane Boulden (Everything Open 2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 12회"},"navigationEndpoint":{"clickTrackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=WwLSPc01A6E","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"WwLSPc01A6E","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-jwwy.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=5b02d23dcd3503a1\u0026ip=1.208.108.242\u0026initcwndbps=4167500\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiFAoYfU6dzHtIFbqgEiUExJM3l1M29CWUNwajVic1NiazBhUGJ0TDR5RTRWMUZfOA==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 12회"}},"simpleText":"조회수 12회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CNYCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNYCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"WwLSPc01A6E","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CNYCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["WwLSPc01A6E"],"params":"CAQ%3D"}},"videoIds":["WwLSPc01A6E"],"videoCommand":{"clickTrackingParams":"CNYCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=WwLSPc01A6E","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"WwLSPc01A6E","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-jwwy.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=5b02d23dcd3503a1\u0026ip=1.208.108.242\u0026initcwndbps=4167500\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CNYCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CNUCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNUCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtXd0xTUGMwMUE2RQ%3D%3D"}}}}}},"trackingParams":"CNUCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtXd0xTUGMwMUE2RQ%3D%3D","commands":[{"clickTrackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CNQCEI5iIhMIqqfUjJqIkgMVYbZWAR3jHyIh","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","hasSeparator":true}}],"trackingParams":"CNECEJQ1GAEiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"28분 24초"}},"simpleText":"28:24"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CNMCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"WwLSPc01A6E","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CNMCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"WwLSPc01A6E"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CNMCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CNICEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNICEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"WwLSPc01A6E","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CNICEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["WwLSPc01A6E"],"params":"CAQ%3D"}},"videoIds":["WwLSPc01A6E"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CNICEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"j_2Fk4un_aY","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/j_2Fk4un_aY/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARh_IBMoODAP\u0026rs=AOn4CLC4UNco1XrvwWMHunQd_kDZ3HhzLg","width":168,"height":94},{"url":"https://i.ytimg.com/vi/j_2Fk4un_aY/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARh_IBMoODAP\u0026rs=AOn4CLC9fdjbUHGfa5ycTQbZDKHsfq5OqA","width":196,"height":110},{"url":"https://i.ytimg.com/vi/j_2Fk4un_aY/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYfyATKDgwDw==\u0026rs=AOn4CLDxVi7RDb73-T6oDy8RVZIC_JqCEg","width":246,"height":138},{"url":"https://i.ytimg.com/vi/j_2Fk4un_aY/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYfyATKDgwDw==\u0026rs=AOn4CLDLFDPblwxOJjOJ_vKRXIa0FfaLkw","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Why 99% Of WordPress Vulnerabilities Are Utterly Irrelevant - Cameron Jones (Everything Open 2025) 43분"}},"simpleText":"Why 99% Of WordPress Vulnerabilities Are Utterly Irrelevant - Cameron Jones (Everything Open 2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 13회"},"navigationEndpoint":{"clickTrackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=j_2Fk4un_aY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"j_2Fk4un_aY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=8ffd85938ba7fda6\u0026ip=1.208.108.242\u0026initcwndbps=4201250\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiFApvuf3biy4f6PAaoBIlBMSTN5dTNvQllDcGo1YnNTYmswYVBidEw0eUU0VjFGXzg=","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 13회"}},"simpleText":"조회수 13회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CNACEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNACEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"j_2Fk4un_aY","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CNACEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["j_2Fk4un_aY"],"params":"CAQ%3D"}},"videoIds":["j_2Fk4un_aY"],"videoCommand":{"clickTrackingParams":"CNACEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=j_2Fk4un_aY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"j_2Fk4un_aY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=8ffd85938ba7fda6\u0026ip=1.208.108.242\u0026initcwndbps=4201250\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CNACEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CM8CEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM8CEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtqXzJGazR1bl9hWQ%3D%3D"}}}}}},"trackingParams":"CM8CEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtqXzJGazR1bl9hWQ%3D%3D","commands":[{"clickTrackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CM4CEI5iIhMIqqfUjJqIkgMVYbZWAR3jHyIh","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","hasSeparator":true}}],"trackingParams":"CMsCEJQ1GAIiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"43분 7초"}},"simpleText":"43:07"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CM0CEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"j_2Fk4un_aY","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CM0CEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"j_2Fk4un_aY"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CM0CEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CMwCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMwCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"j_2Fk4un_aY","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CMwCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["j_2Fk4un_aY"],"params":"CAQ%3D"}},"videoIds":["j_2Fk4un_aY"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CMwCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"oLwnGCAuwQg","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/oLwnGCAuwQg/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLC2-3inBytgyzfga_Iqcl2_e4B0RA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/oLwnGCAuwQg/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLCgJbB_XmljU8xE6E5LoQZ8f5Y-9Q","width":196,"height":110},{"url":"https://i.ytimg.com/vi/oLwnGCAuwQg/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLDqUVx2wwweSLjEPfjYfAzjV0AJAA","width":246,"height":138},{"url":"https://i.ytimg.com/vi/oLwnGCAuwQg/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLCsMs6RMS77E4ZcAZ3iDMdNKf3Q8w","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Did you get my message? - Paul Schulz (Everything Open 2025) 43분"}},"simpleText":"Did you get my message? - Paul Schulz (Everything Open 2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 12회"},"navigationEndpoint":{"clickTrackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oLwnGCAuwQg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oLwnGCAuwQg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a0bc2718202ec108\u0026ip=1.208.108.242\u0026initcwndbps=4201250\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiFAiIK7gYLjid6gAaoBIlBMSTN5dTNvQllDcGo1YnNTYmswYVBidEw0eUU0VjFGXzg=","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 12회"}},"simpleText":"조회수 12회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CMoCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMoCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"oLwnGCAuwQg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CMoCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["oLwnGCAuwQg"],"params":"CAQ%3D"}},"videoIds":["oLwnGCAuwQg"],"videoCommand":{"clickTrackingParams":"CMoCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oLwnGCAuwQg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oLwnGCAuwQg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a0bc2718202ec108\u0026ip=1.208.108.242\u0026initcwndbps=4201250\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CMoCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CMkCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMkCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtvTHduR0NBdXdRZw%3D%3D"}}}}}},"trackingParams":"CMkCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtvTHduR0NBdXdRZw%3D%3D","commands":[{"clickTrackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CMgCEI5iIhMIqqfUjJqIkgMVYbZWAR3jHyIh","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","hasSeparator":true}}],"trackingParams":"CMUCEJQ1GAMiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"43분 23초"}},"simpleText":"43:23"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CMcCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"oLwnGCAuwQg","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CMcCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"oLwnGCAuwQg"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CMcCEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CMYCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMYCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"oLwnGCAuwQg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CMYCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["oLwnGCAuwQg"],"params":"CAQ%3D"}},"videoIds":["oLwnGCAuwQg"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CMYCEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"bih6HAhrdxI","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/bih6HAhrdxI/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARh_IB4oEzAP\u0026rs=AOn4CLAgFvV3F9dOlLWfsA_gGFdvHV0FJA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/bih6HAhrdxI/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARh_IB4oEzAP\u0026rs=AOn4CLA8bjLYPEUcIjjZUvQRH1H5NO-xKg","width":196,"height":110},{"url":"https://i.ytimg.com/vi/bih6HAhrdxI/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYfyAeKBMwDw==\u0026rs=AOn4CLAmqND3bD57MOf7JGN1g_EoGljD1g","width":246,"height":138},{"url":"https://i.ytimg.com/vi/bih6HAhrdxI/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYfyAeKBMwDw==\u0026rs=AOn4CLALU3eu0trL5WOapedwnQ2Bloc46w","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Open source your code, not your keys and secrets - Alistair Chapman (Everything Open 2025) 44분"}},"simpleText":"Open source your code, not your keys and secrets - Alistair Chapman (Everything Open 2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 23회"},"navigationEndpoint":{"clickTrackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=bih6HAhrdxI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"bih6HAhrdxI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-bh2e6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=6e287a1c086b7712\u0026ip=1.208.108.242\u0026initcwndbps=2991250\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiFAku6tw8DDnpRuqgEiUExJM3l1M29CWUNwajVic1NiazBhUGJ0TDR5RTRWMUZfOA==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 23회"}},"simpleText":"조회수 23회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CMQCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMQCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"bih6HAhrdxI","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CMQCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["bih6HAhrdxI"],"params":"CAQ%3D"}},"videoIds":["bih6HAhrdxI"],"videoCommand":{"clickTrackingParams":"CMQCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=bih6HAhrdxI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"bih6HAhrdxI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-bh2e6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=6e287a1c086b7712\u0026ip=1.208.108.242\u0026initcwndbps=2991250\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CMQCEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CMMCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMMCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtiaWg2SEFocmR4SQ%3D%3D"}}}}}},"trackingParams":"CMMCEJSsCRgGIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtiaWg2SEFocmR4SQ%3D%3D","commands":[{"clickTrackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CMICEI5iIhMIqqfUjJqIkgMVYbZWAR3jHyIh","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","hasSeparator":true}}],"trackingParams":"CL8CEJQ1GAQiEwiqp9SMmoiSAxVhtlYBHeMfIiE=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"44분 48초"}},"simpleText":"44:48"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CMECEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"bih6HAhrdxI","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CMECEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"bih6HAhrdxI"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CMECEPnnAxgBIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CMACEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMACEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"bih6HAhrdxI","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CMACEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["bih6HAhrdxI"],"params":"CAQ%3D"}},"videoIds":["bih6HAhrdxI"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CMACEMfsBBgCIhMIqqfUjJqIkgMVYbZWAR3jHyIh"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"dNfXag6HW20","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/dNfXag6HW20/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLCqmFFavswJ0n-60DgX4jKOAjh7Fg","width":168,"height":94},{"url":"https://i.ytimg.com/vi/dNfXag6HW20/hqdefault.jpg?sqp=-oaymwE8CMQBEG5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARhlIGUoZTAP\u0026rs=AOn4CLAvmSB6246qmH0RB5IuTjVwPF0tRQ","width":196,"height":110},{"url":"https://i.ytimg.com/vi/dNfXag6HW20/hqdefault.jpg?sqp=-oaymwE9CPYBEIoBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLAxOqWnmkduSNawjsaEVY4laIKPYg","width":246,"height":138},{"url":"https://i.ytimg.com/vi/dNfXag6HW20/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYZSBlKGUwDw==\u0026rs=AOn4CLBjdeba-QBLA2A9gA4IeUN58ZtRkw","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"대학에서 오픈 소스를 가르치면서 배운 것들 - 블라디미르 루다코프(Everything Open 2025) 37분"}},"simpleText":"대학에서 오픈 소스를 가르치면서 배운 것들 - 블라디미르 루다코프(Everything Open 2025)"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 32회"},"navigationEndpoint":{"clickTrackingParams":"CLkCEJQ1GAUiEwiqp9SMmoiSAxVhtlYBHeMfIiEyBmctaGlnaFoYVUNkRW5PZ1IzcmNZZklwemRBYzhRc1JRmgEFEPI4GGSqASJQTEkzeXUzb0JZQ3BqNWJzU2JrMGFQYnRMNHlFNFYxRl84ygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=dNfXag6HW20","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"dNfXag6HW20","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=74d7d76a0e875b6d\u0026ip=1.208.108.242\u0026initcwndbps=4201250\u0026mt=1768296063\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Everything Open","navigationEndpoint":{"clickTrackingParams":"CLkCEJQ1GAUiEwiqp9SMmoiSAxVhtlYBHeMfIiHKAQQBpmgv","commandMetadata":{"webCommandMetadata":{"url":"/@EverythingOpen","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCdEnOgR3rcYfIpzdAc8QsRQ","canonicalBaseUrl":"/@EverythingOpen"}}}]},"trackingParams":"CLkCEJQ1GAUiEwiqp9SMmoiSAxVhtlYBHeMfIiFA7bad9KDt9et0qgEiUExJM3l1M29CWUNwajVic1NiazBhUGJ0TDR5RTRWMUZfOA==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 32회"}},"simpleText":"조회수 32회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CL4CEP6YBBgFIhMIqqfUjJqIkgMVYbZWAR3jHyIhygEEAaZoLw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions" | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#reflect-tunnel-2110485 | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/api/suites-api.html | Suites API | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Developer API Suites API Suites API Execute suites and retrieve results via CI/CD and other external systems. List all suites List all suites in your account. Request GET https://api.reflect.run/v1/suites Response { "suites": { "data": [ { "name": "Regression Tests", "suiteId": "regression-tests", "created": 1638416940 } ] } } Response Fields suites object: A wrapped collection of abridged suites. suites.data.name string: The suite name. suites.data.suiteId string: The suite identifier. suites.data.created number: The suite's creation timestamp as an epoch in seconds. List suite executions List recent executions for a given suite. Request GET https://api.reflect.run/v1/suites/<suite-id>/executions Response { "suiteId": "regression-tests", "executions": { "data": [ { "executionId": 47, "url": "https://app.reflect.run/suites/regression-tests/executions/47", "isFinished": false, "status": "pending" } ] } } Response Fields suiteId string: The suite identifier. executions object: A wrapped collection of abridged executions. suites.data.executionId number : The suite execution identifier. suites.data.url string: The in-app URL that displays information and results about the suite execution. suites.data.isFinished boolean: A boolean indicating whether the suite execution has completed. suites.data.status string: One of: pending, canceled, passed or failed. Summarizes the state of the execution from its test instances.One of: pending, canceled, passed or failed. Summarizes the state of the execution from its test instances. Execute a suite Triggers an execution of the specified suite. The suite-id value for your suite should match the ID value displayed on the Suite Detail page, including casing. (See Integrating via API .) Reflect identifies certain properties of a scheduled execution as “reserved”. These reserved fields can be overridden with values provided by the API request: hostnames : Allows you to specify a replacement hostname value for a given target hostname. cookies: Allows you to specify cookies that will be set when loading the test’s initial URL. A cookie consists of the following fields: name (required string): The name of the cookie to be set. value (required string): The cookie’s value. domain (optional string): Host to which the cookie will be sent. Defaults to the host of the test’s initial URL. expires (optional number): Epoch timestamp (in milliseconds) indicating when the cookie should be deleted. If unspecified, the cookie becomes a session cookie. httpOnly (optional boolean): Indicates the cookie should be inaccessible to JavaScript on the page and only sent to the server. maxAge (optional number): Number of milliseconds until the cookie expires. If both expires and maxAge are set, maxAge has precedence. path (optional string): A URL path that must exist in a request URL in order to include the cookie in a request. secure (optional boolean): Indicates that the cookie should only be sent to the server when a request is made with https:. headers : Allows you to specify headers that will be sent when loading the test’s initial URL. name (required string): The name of the header. value (required string): The header value. persist (optional boolean): Specifies whether this header should only be set in the initial request or for every subsequent HTTP request (ex: when overriding the Accept-Language header). If set to true , the Authorization header is only set for requests that match the hostname of the test’s original URL. Defaults to false . localStorage and sessionStorage : Allows you to specify local and session storage values to be set on the test’s initial URL. The variables field allows you to specify a definition for a variable or parameter used in the tests. Finally, if your Reflect account has OAuthed with GitHub , you can specify a repository, its owner, and a commit SHA in the request to have Reflect automatically post a commit status to GitHub as the suite’s execution progresses. Request POST https://api.reflect.run/v1/suites/<suite-id>/executions Response { "overrides": { "agent": { "name": "agent-name" }, "hostnames": [{ "original": "prod.myapp.com", "replacement": "staging.myapp.com" }], "cookies": [{ "name": "my-favorite-cookie", "value": "chocolate-chip", "domain": "myapp.com", "expires": 123456789, "httpOnly": false, "maxAge": 123, "path": "/", "secure": true }], "headers": [{ "name": "X-Custom-Header", "value": "custom-value", "persist": false }], "localStorage": [{ "key": "my-local-key", "value": "local-value" }], "sessionStorage": [{ "key": "my-session-key", "value": "session-value" }] }, "variables": { "username1": "user+${alpha(8)}@example.com", "password": "acompletelyunguessablepassword" }, "gitHub": { "owner": "repository-owner", "repo": "my-repository-name", "sha": "0f4212320f2cb6734583ebef3a4928d78d4f3fde" } } Request Fields overrides optional object: Overrides to apply to properties of all tests executed in this scheduled execution. agent (object, optional) name (string, required) : The name of the Tunnel/Agent to use for this execution. variables optional object: Collection of ('name', 'definition') variable overrides to apply to this scheduled execution. gitHub optional object: An object specifying the GitHub repository name, its owner, and commit SHA to post the status of the execution. Response { "suiteId": "regression-tests", "executionId": 3878, "overrides": { "hostnames": [ { "original": "prod.myapp.com", "replacement": "staging.myapp.com" } ] }, "gitHub": { "owner": "repository-owner", "repo": "my-repository-name", "sha": "0f4212320f2cb6734583ebef3a4928d78d4f3fde" }, "url": "https://app.reflect.run/suites/regression-tests/executions/3878", "isFinished": false, "status": "pending", "tests": { "data": [], "bookmark": "" } } Response Fields suiteId string: The identifier specified in the execution request. executionId number: The unique numeric identifier assigned to the suite execution. overrides optional object: Overrides applied to properties of all tests executed in this suite. gitHub optional object: An object specifying the GitHub repository name, its owner, and commit SHA to post the status of the execution. url string: The in-app URL that displays information and results about the suite execution. isFinished boolean: A boolean indicating whether the suite execution has completed. status string: One of: pending, canceled, passed or failed. Summarizes the state of the execution from its test instances. tests object: A wrapped collection of test instances (test definition &amp; execution configuration) with individual test runs. tests.bookmark optional string: Reserved for future - used to read additional test instances. Execute a data-driven suite Similar to the execute a suite endpoint, this endpoint invokes a Reflect test suite with a set of optional overrides. However, this endpoint has the additional capability of accepting a set of data-driven values in a CSV file. Those values are used to override the (test, parameters) pairs for a specific Run Tests action in the Suite. Multiple CSV files can be sent to override different Run Tests actions. Note This endpoint requires sending data in a multipart request, consisting of: One or more CSV files in the format outlined in Request CSV file format . A single application/json part containing the fields described in Request JSON Fields . Request POST https://api.reflect.run/v1/suites/<suite-id>/executions/data-driven Or via curl through the following command: curl \ -H 'X-API-KEY: <API-KEY>' \ -F 'config={"actionNameByFilename": {"one.csv": "run-tests-1", "two.csv": "run-tests-2"}};type=application/json' \ -F [email protected] \ -F [email protected] \ https://api.reflect.run/v1/suites/<suite-id>/executions/data-driven Request CSV file format Each CSV file in the request should be in the following format: Test Name or ID,Parameter One,Parameter Two,Parameter Three 1,value one,${var(one)},value three 1,,value two,${var(two)} two,value one,value two,value three The first column is the ID or name of a Test, all columns that follow are values for the parameter names specified in the header row of the CSV. Note that any column whose value is left empty will not be overridden. For example, in the second data row ‘Parameter One’ is not overridden with any value. Request JSON Fields actionNameByFilename object: Collection of ('CSV file name', 'Custom Action Name') pairs, where the 'Custom Action Name' is the custom name you have assigned to a Run Tests action in the Suite. overrides optional object: Overrides to apply to properties of all tests executed in this scheduled execution. See 'Execute a suite' for details on the properties that can be overridden. variables optional object: Collection of ('name', 'definition') variable overrides to apply to this scheduled execution. gitHub optional object: An object specifying the GitHub repository name, its owner, and commit SHA to post the status of the execution. Response Fields suiteId string: The identifier specified in the execution request. executionId number: The unique numeric identifier assigned to the suite execution. overrides optional obejct: Overrides applied to properties of all tests executed in this suite. gitHub optional object: An object specifying the GitHub repository name, its owner, and commit SHA to post the status of the execution. url string: The in-app URL that displays information and results about the suite execution. isFinished boolean: A boolean indicating whether the suite execution has completed. status string: One of: pending, canceled, passed or failed. Summarizes the state of the execution from its test instances. tests object: A wrapped collection of test instances (test definition &amp; execution configuration) with individual test runs. tests.bookmark optional string: Reserved for future - used to read additional test instances. Get execution status Returns the completion status of the specified suite. Request : GET https://api.reflect.run/v1/suites/<suite-id>/executions/<execution-id> Response { "suiteId": "regression-tests", "executionId": 36, "overrides": { "hostnames": [ { "original": "prod.myapp.com", "replacement": "staging.myapp.com" } ] }, "gitHub": { "owner": "repository-owner", "repo": "my-repository-name", "sha": "0f4212320f2cb6734583ebef3a4928d78d4f3fde" }, "url": "https://app.reflect.run/suites/regression-tests/executions/36", "isFinished": true, "status": "passed", "tests": { "data": [ { "instanceId": 0, "testId": 683, "actionName": "run-tests-1", "startingUrl": "https://staging.myapp.com/test-one", "status": "passed", "runs": [ { "runId": 2641, "browser": "Chrome", "status": "passed", "variables": {}, "startTime": 1643734963077, "endTime": 1643734979203, "runTime": 16126, "timestamp": 1643734979647, "videoUrl": "https://reflect-videos.s3.amazonaws.com/2641_969e.mp4", "stepCount": 14 } ] }, { "instanceId": 1, "testId": 686, "startingUrl": "https://staging.myapp.com/test-two", "status": "passed", "runs": [ { "runId": 2642, "browser": "Chrome", "status": "passed", "variables": {}, "startTime": 1643734994863, "endTime": 1643735012070, "runTime": 17207, "timestamp": 1643735012534, "videoUrl": "https://reflect-videos.s3.amazonaws.com/2641_89f7.mp4", "stepCount": 9 } ] }, { "instanceId": 2, "testId": 688, "startingUrl": "https://staging.myapp.com/test-three", "status": "failed", "runs": [ { "runId": 2643, "browser": "Chrome", "status": "failed", "variables": {}, "startTime": 1643734996842, "endTime": 1643735012095, "runTime": 15253, "timestamp": 1643735012539, "videoUrl": "https://reflect-videos.s3.amazonaws.com/2641_4e95.mp4", "stepCount": 6, "failedStepIndex": { "4": "Visual Observe Failed - image difference exceeds limit", "5": "Element Selection Failed" } } ] } ], "bookmark": "" } } Response Fields suiteId string: The identifier specified in the execution request. executionId number: The unique numeric identifier assigned to the suite execution. overrides optional object: Overrides applied to properties of all tests executed in this suite. gitHub optional object: An object specifying the GitHub repository name, its owner, and commit SHA to post the status of the execution. url string: The in-app URL that displays information and results about the suite execution. isFinished boolean: A boolean indicating whether the suite execution has completed. status string: One of: pending, canceled, passed or failed. tests object: A wrapped collection of test instances (test definition &amp; execution configuration) with individual test runs. tests.bookmark optional string: Reserved for future - used to read additional test instances. tests.data.instanceId number: The identifier for a logical test instance (definition &amp; configuration) in the execution. tests.data.testId number: The identifier for the test. tests.data.actionName optional string: The name assigned to the Run Tests action the instance originated from, if one was given. tests.data.startingUrl string: The initial URL used by the test, accounting for any user-specified overrides. tests.data.status string: One of: pending, passed or failed. Summarizes the outcome of the test instance from its runs. tests.data.runs object: An array of test runs for a single test instance, with completion timestamp and status. tests.data.runs.browser string: The browser used to execute this test run. One of: Chrome, Edge, Firefox, or Safari. tests.data.runs.status string: The outcome of the test run. Either passed or failed. tests.data.runs.variables object: The variables that were used or created by the test run. tests.data.runs.startTime number: Timestamp of when the test run started. tests.data.runs.endTime number: Timestamp of when the test run stopped. tests.data.runs.runTime number: Total time that the test run spent running (endTime - startTime). tests.data.runs.timestamp number: Timestamp that the test run's execution was recorded in Reflect . tests.data.runs.videoUrl string: The URL of a video recording of the test run. tests.data.runs.stepCount number: The number of steps in the executed definition. tests.data.runs.failedStepIndex optional object: A dictionary containing the failed steps from the test run. The key represents the index of the step (zero-based), and the value is a summary error message describing the failure encountered during that step. Only defined when the status of the run is failed. Cancel an execution Attempts to cancel the specified suite execution. Request PATCH https://api.reflect.run/v1/suites/<suite-id>/executions/<execution-id>/cancel Response { "suiteId": "regression-tests", "executionId": 3878, "success": true } Response Fields suiteId string: The identifier specified in the execution request. executionId number: The unique numeric identifier assigned to the suite execution. success boolean: A boolean indicating whether the suite execution was successfully canceled. In this section : Suites API List all suites List suite executions Execute a suite Execute a data-driven suite Request Response Fields Get execution status Cancel an execution Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#configuring-access | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.atlassian.com/ko/itsm | ITSM: IT 서비스 관리 정의, 이점 및 도구 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 제품 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 모든 앱 보기 추천 추천 앱 Jira 유연한 프로젝트 관리 Confluence 공동 작업 중심의 지식 작업 영역 Jira Service Management 빠른 속도의 서비스 제공 Atlassian Collection 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align 신속한 서비스 제공 Jira Service Management • Customer Service Management • 자산 • Rovo 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass 제공: Rovo 팀의 지식으로 구동되는 AI 기반 앱. 개발자 Jira 유연한 프로젝트 관리 Compass 팀을 위한 소프트웨어 카탈로그 파이프라인 확장 가능한 CI/CD 자동화 Bitbucket 소스 코드 및 CI/CD DX (인수 보류 중) 생산성 및 AI 영향 측정 Rovo Dev 개발자를 위한 에이전틱 AI 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo 팀의 지식으로 구동되는 AI 기반 앱. 제품 매니저 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Jira Product Discovery 신규 아이디어 캡처 및 우선 순위 지정 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. IT 전문가 Jira Service Management 빠른 속도의 서비스 제공 Guard 신규 향상된 클라우드 보안 Rovo 팀의 지식으로 구동되는 AI 기반 앱. 비즈니스 팀 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Trello 체계적이고 시각화된 작업 Loom 신규 빠른 비동기식 동영상 업데이트 Jira Service Management 빠른 속도의 서비스 제공 Customer Service Management Customer experiences reimagined 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. 리더십 팀 Focus 신규 엔터프라이즈급 전략 계획 Talent 신규 지식 인력 계획 Jira Align 엔터프라이즈 전체에 걸친 작업 계획 및 가치 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back 솔루션 솔루션 사용 사례별 팀 협업 전략 및 계획 서비스 매니지먼트 소프트웨어 개발 팀별 소프트웨어 마케팅 IT 크기별 Enterprise 소규모 비즈니스 Startup 비영리 기관 업계별 리테일 통신 프로페셔널 서비스 정부 Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back Atlassian을 선택하는 이유 Atlassian을 선택하는 이유 업무 시스템 신규 팀 협업 방식에 대한 Atlassian의 블루프린트 통합 수천 개의 앱을 Atlassian 제품에 연결 고객 팀워크 기반의 사례 연구 및 스토리 FedRAMP 공공 부문을 위한 규정 준수 솔루션 복원력 엔터프라이즈급 및 고성능 인프라 플랫폼 고도로 통합되고 신뢰할 수 있는 안전한 플랫폼 Trust Center 데이터의 보안, 컴플라이언스 및 가용성 보장 Back 리소스 리소스 고객 지원 질문하고 버그를 신고하고 피드백을 제공 파트너 찾기 컨설팅, 교육 및 제품 사용자 지정 지원 Atlassian Ascend 전환을 위한 리소스 및 지원 커뮤니티 Atlassian 커뮤니티와 함께 배우고 소통하며 성장하세요 지원 일반적인 질문 제품 조언 파트너 지원 Enterprise 지원 기술 지원 가격 및 청구 개발자 지원 구매 및 라이선싱 리소스 프로젝트 관리 애자일 Atlassian Learning 시작하기 프로젝트 협업 팀 플레이북 제품 문서 Back Enterprise 자세한 내용 + 간략히 보기 - 무료로 시작 Jira 유연한 프로젝트 관리 Jira Service Management 빠른 속도의 서비스 제공 Confluence 모두 한곳에 있는 지식 제품 모두 보기 무료로 시작 Back 무료로 시작 ITSM Open and close the navigation menu 리소스 Jira Service Management 인시던트 관리 제품 가이드 리소스 라이브러리 IT 운영, 개발 및 비즈니스 팀을 위한 서비스 관리 규모에 맞게 빠른 속도로 서비스 관리를 지원합니다. 무료로 시작 자세히 알아보기 인시던트에 대응하고, 인시던트를 해결하며, 인시던트로부터 배우는 방법 서비스를 운영 상태로 복원하기 위한 Atlassian의 팁을 참조하세요. 자세히 알아보기 JSM을 설정하기 위해 알아야 할 모든 사항 이 가이드는 기본 정보부터 심층적인 모범 사례까지 모든 내용을 다루고 있습니다. 가이드 보기 Jira Service Management 리소스 라이브러리 백서, 사례 연구, 보고서 등을 살펴보고 필요한 모든 정보를 얻으세요. 라이브러리 보기 무료로 시작 리소스 Jira Service Management 인시던트 관리 제품 가이드 리소스 라이브러리 IT 운영, 개발 및 비즈니스 팀을 위한 서비스 관리 규모에 맞게 빠른 속도로 서비스 관리를 지원합니다. 무료로 시작 자세히 알아보기 인시던트에 대응하고, 인시던트를 해결하며, 인시던트로부터 배우는 방법 서비스를 운영 상태로 복원하기 위한 Atlassian의 팁을 참조하세요. 자세히 알아보기 JSM을 설정하기 위해 알아야 할 모든 사항 이 가이드는 기본 정보부터 심층적인 모범 사례까지 모든 내용을 다루고 있습니다. 가이드 보기 Jira Service Management 리소스 라이브러리 백서, 사례 연구, 보고서 등을 살펴보고 필요한 모든 정보를 얻으세요. 라이브러리 보기 IT 지원이란? 무료로 시작 자세히 알아보기 서비스 요청 관리 개요 서비스 데스크 구축을 위한 모범 사례 IT 메트릭 및 보고 SLA: 정의, 이유 및 방법 FCR(First Call Resolution)이 중요한 이유 지원 센터 서비스 데스크, 지원 센터 및 ITSM 비교 IT 지원을 DevOps 방식으로 실행하는 방법 대화형 티켓팅 Jira Service Management 사용자 지정 이메일 지원에서 전환 서비스 카탈로그 가상 에이전트란? IT 지원 IT 서비스 포털 IT 티켓 시스템 IT 자산 관리 개요 구성 관리 데이터베이스 구성 및 자산 관리 비교 IT 및 소프트웨어 자산 관리 모범 사례 자산 추적 하드웨어 자산 관리 자산 관리 수명 주기 인시던트 관리 개요 IT 서비스 연속성 관리 인시던트 커뮤니케이션 템플릿 워크숍 인시던트 대응 모범 사례 인시던트 관제자 항공 역할 및 책임 수명 주기 플레이북 IT 지원 수준 대기 중 담당자 대기 일정 대기 근무 급여 알림 피로 대기 근무 개선 IT 알림 에스컬레이션 정책 도구 위기 관리 템플릿 에스컬레이션 경로 템플릿 KPI 일반 메트릭 심각도 수준 가동 중지 시간으로 인한 비용 SLA, SLO, SLI 비교 오류 예산 신뢰성 및 가용성 비교 MTTF(평균 장애 시간) DevOps SRE 직접 구축하고 직접 운영 문제 관리와 인시던트 관리 비교 ChatOps ITSM 주요 인시던트 관리 IT 인시던트 관리 IT 운영을 위한 최신 인시던트 관리 IT 재해 복구 계획을 개발하는 방법 재해 복구 계획 예시 버그 추적 모범 사례 사후 검토 템플릿 비난 배제 보고서 미팅 타임라인 5개 이유 공개 및 비공개 비교 튜토리얼 인시던트 커뮤니케이션 대기 중 담당자 일정 고객 알림 자동화 핸드북 인시던트 대응 사후 검토 템플릿 생성기 용어집 핸드북 받기 2020년도 인시던트 관리 현황 2021년 인시던트 관리 현황 IT 관리 개요 문제 관리 개요 템플릿 역할 및 책임 프로세스 변경 관리 개요 모범 사례 역할 및 책임 변경 자문 위원회 변경 관리 유형 변경 관리 프로세스 지식 관리 개요 기술 자료의 정의 지식 중심 서비스(KCS)란 무엇입니까 셀프 서비스 기술 자료 엔터프라이즈 서비스 관리 개요 HR 서비스 관리 및 제공 HR 자동화 모범 사례 ESM에 대한 세 가지 구현 팁 오프보딩 프로세스 이해 직원 경험 관리 전략 최고의 온보딩 소프트웨어 9가지 직원 경험 플랫폼 온보딩 워크플로 직원 온보딩 체크리스트 IT 서비스 제공 HR 헬프 데스크 소프트웨어 HR 서비스 센터 HR 케이스 관리 변경 관리 도구 HR 자동화 HR 프로세스 개선 데이터 거버넌스 HR 서비스 제공 모델 HR 지식 관리 HR 워크플로 자동화 ITIL 개요 DevOps 및 ITIL 비교 ITIL 서비스 전략 가이드 ITIL 서비스 전환 지속적인 서비스 개선 IT 운영 개요 IT 인프라 관리 네트워크 인프라 IT 운영 관리 개요 시스템 업그레이드 서비스 매핑 애플리케이션 종속성 매핑 IT 인프라 IT 서비스 관리(ITSM)란 무엇입니까? ITSM이라고도 하는 IT 서비스 관리는 간략하게 IT 팀에서 처음부터 끝까지 IT서비스를 고객에게 전달하는 방법입니다. 여기에는 IT 서비스의 설계, 제작, 제공 및 지원에 이르는 모든 과정과 활동이 포함됩니다. ITSM의 핵심 개념은 IT가 하나의 서비스로 작동해야 한다는 신념입니다. 일반적인 ITSM 시나리오에는 노트북과 같은 새 하드웨어를 요청하는 상황이 포함될 수 있습니다. 포털을 통해 요청을 제출하고 티켓에 모든 관련 정보가 포함된 티켓을 제출하고 반복 가능한 워크플로를 시작합니다. 그러면 티켓이 IT 팀 큐에 도착하게 되며 받은 요청은 중요도에 따라 정렬 및 처리됩니다. ITSM을 위한 Atlassian IT 제공, 운영 및 지원 전반에 걸쳐 Atlassian을 활용한 ITSM에 대해 알아야 할 기본 사항과 모범 사례 및 팁을 제공합니다. 가이드 보기 IT 팀과의 일상적인 상호 작용 때문에 ITSM은 기본적인 IT 지원으로 오해를 받는 경우가 많습니다. 이 두 가지는 사실 다릅니다. ITSM 팀은 노트북부터 서버, 비즈니스에 핵심적인 소프트웨어 애플리케이션에 이르기까지 모든 종류의 업무용 기술을 관리합니다. IT 팀이 기술 인프라 관리 및 유지 관리에 중점을 두는 반면 ITSM 팀은 특히 조직의 요구 사항과 사용자 기대치를 충족하기 위해 효율적인 IT 서비스를 최적화 및 제공하는 데 전념합니다. IT 업계에서는 ITSM에 대한 적절한 접근 방식이 다음의 세 단계를 순서대로 따라야 한다는 공통적인 인식이 있습니다. 1) IT 기술을 구축 및 구현합니다. 2) 올바른 프로세스를 도입하고 시행합니다. 3) 사용자는 기술을 배우고 프로세스를 따릅니다. Atlassian은 그 패러다임을 뒤집습니다. Atlassian에서는 팀이 최우선 입니다. 팀의 업무 방식을 개선하는 데 도움이 되는 도구를 제공하기 위해 팀 플레이북 도 만들었습니다. IT 팀은 지속적으로 학습하고 개선해야 합니다. 스스로가 가치 있고 회사를 변화시킬 수 있는 권한을 부여받았다고 느껴야 합니다. 계층화된 보고 구조나 엄격한 프로세스에 의한 규칙을 준수하는 대신 IT 팀에서는 SLA 채택 및 구현해야 하는 소프트웨어에 대해 정보에 기반한 의사 결정을 내릴 수 있습니다. 강력한 IT 팀은 생산성을 높이고 디지털 혁신을 주도하는 데 중추적인 역할을 하므로 기업 성과를 높이는 데 없어서는 안 될 존재입니다. IT 팀은 ITSM(IT 서비스 관리) 프로세스 및 기술의 핵심입니다. IT 팀의 강점에 집중한 후에는 회사에 가치를 제공하는 고유한 관행과 역량을 개발할 수 있습니다. 아무리 평판이 좋은 소스라도 단순히 다른 회사의 표준을 "복사하여 붙여 넣고" 해당 표준이 귀하의 고유한 환경에서 효과가 있기를 바라는 것만으로는 충분하지 않습니다. 성공적인 IT 팀은 ITIL(정보 기술 인프라 라이브러리) 과 같은 프레임워크를 활용하고 고객의 요구 사항과 선호도에 맞게 정렬하도록 프로세스를 신중하게 조정하여 접근 방식을 수립합니다. 마지막으로 소프트웨어나 및 기술은 팀의 관행을 지원하고 그 영향력을 확대해야 합니다. 최고의 ITSM 소프트웨어 는 팀 간의 공동 작업을 지원하고 최종 사용자의 역량을 강화하고 일상적이거나 반복적인 작업을 자동화하여 모두가 가장 중요한 일에 집중할 수 있는 시간을 더 많이 제공합니다. 기술이 방해가 되어 불필요한 복잡성과 불만을 유발하는 경우를 모두 본 적 있을 것입니다. 기술이 원활하게 작동하면 마법과도 같이 보일 수 있지만 실제로는 기술을 사용하는 팀의 상당한 노력이 반영되어 있는 것입니다. IT 서비스란 무엇입니까? ITSM에서 IT 서비스는 최종 사용자 또는 고객에게 기술과 관련된 지원과 솔루션을 제공하는 것을 의미합니다. 여기에는 노트북, 서버 및 비즈니스에 핵심적인 소프트웨어 애플리케이션을 포함한 광범위한 업무용 기술이 포함됩니다. ITSM 팀은 구조화된 프로세스를 통해 이러한 서비스와 관련된 요청 및 인시던트를 처리하여 서비스 효율성, 신뢰성 및 사용자 만족을 보장합니다. ITSM 프레임워크란 무엇입니까? 프레임워크는 ITSM에 표준화된 관행 및 절차를 제공하는 도구입니다. 프레임워크는 서비스 제공 및 지원을 위해 지속적 개선 을 모니터링하는 플랫폼을 제공할 수 있습니다. ITSM은 다양한 IT 기능에 대한 서비스를 제공하는 IT 서비스 관리 프레임워크입니다. 기본 시스템 운영에 효율성과 가치를 제공하는 운영 절차, 기술 및 지원 서비스를 정의합니다. 프레임워크는 회사가 ITSM 전략을 정의하는 데 도움이 됩니다. 인기 있는 ITSM 프레임워크 IT 팀은 다양한 프레임워크를 사용하여 작업을 이끌어 나갑니다. 가장 일반적인 두 가지 프레임워크는 ITSM과 DevOps입니다. 다른 개념으로는 COBIT, SIAM, IT4IT, 린 등이 있습니다. 아래에서는 최신 IT 팀에 가장 큰 영향을 주는 두 가지 프레임워크인 ITSM 및 DevOps, 그리고 ITSM에 대한 일반적인 접근 방식을 함께 다룰 것입니다. 몇 가지 주요 용어를 정의하면서 시작하겠습니다. ITSM 위에서 설명한 것과 같이 IT 서비스 관리는 IT 팀이 고객에게 IT 서비스를 제공하는 것을 관리하는 방식입니다. ITSM에 대한 팀의 접근 방식은 ITIL 관행에 정렬되어 구조화되고 DevOps 개념의 영향을 받을 수 있습니다. ITIL ITIL 은 ITSM에 대해 가장 널리 수용되는 접근 방식입니다. ITIL은 비즈니스 요구 사항에 맞게 IT 서비스를 정렬하는 관행에 초점을 맞춥니다. ITIL은 회사가 지속적인 혁신과 확장에 적응하는 데 도움이 될 수 있습니다. ITIL 표준에 대한 최신 업데이트인 ITIL 4는 IT 팀에게 패러다임의 전환을 의미합니다. ITIL 4는 팀이 총체적인 비즈니스 및 고객 가치의 기준틀을 만들도록 안내하며 팀의 업무 방식에 따라 더 유연한 접근 방식을 장려합니다. ITIL 4 기본 원칙은 공동 작업, 단순성 및 피드백을 장려합니다. 가끔 ITIL을 가이드가 아닌 "규칙"으로 잘못 표현하는 경우가 있지만 이는 해석의 여지가 있습니다. 프로세스와 문서 작업을 해야 한다고 해서 번거로운 대량의 기록과 관료적 오버헤드가 발생한다는 의미는 아닙니다. 프로세스나 ITIL "규칙" 뒤에 숨는 것은 변명의 여지가 없습니다. DevOps DevOps 는 애자일 및 린 관행을 통해 지원되는 가속화된 IT 서비스 제공에 중점을 둡니다. DevOps는 회사가 소프트웨어를 더 빠르고 안정적으로 구축, 테스트 및 릴리스할 수 있도록 소프트웨어 개발 팀 과 IT 운영 팀 간의 공동 작업을 개선합니다. 신뢰감을 쌓고 소프트웨어 릴리스 속도를 높이고 중요한 이슈를 빠르게 해결하며 계획에 없던 작업을 더 효율적으로 관리하는 것과 같은 주요 이점이 있습니다. DevOps에는 지속적 개발 , 통합 및 자동화된 제공이 포함되지만 그 개념은 지금까지 상대적으로 사일로된 환경에서 일해 온 팀 간에 공동 작업 문화를 구축하는 것에 기반합니다. DevOps의 컨텍스트와 정신의 대부분은 오래된 분열에서 벗어나 협업하는 것입니다. 안타깝게도 이는 'Ops'가 아닌 'Dev'에만 관련된 것으로 간주하는 경우가 많습니다. ITSM과 DevOps는 보통 "ITSM 또는 DevOps" 중에서 '한 쪽만' 선택하도록 하기 때문에 서로 상반된 위치에 있습니다. ITSM 및 DevOps가 제공하는 기능과 이 둘이 함께 작동하는 방식에 대해서는 혼란이 있습니다. 성과가 높은 최신 팀은 더 스마트하고 빠르게 일해야 하는 동시에 여전히 프로세스와 제어가 필요하다는 것을 잘 알고 있습니다. 이제 프레임워크를 명시적으로 따르든 그렇지 않든 ITSM과 DevOps의 극한을 넘어 두 가지 요소를 모두 사용해야 할 때가 왔습니다. DevOps는 단순히 자동화된 개발 그 이상을 의미하며 공동 작업의 중요성과 비난 없는 문화를 장려합니다. 또한 ITSM 및 ITIL 접근 방식을 관리 측면의 부담으로 삼아서는 안 되며 다양한 회사의 고유한 요구 사항에 맞게 애자일 방식으로 사용해야 합니다. ITSM이 중요한 이유는 무엇입니까? ITSM은 IT 팀에 도움이 되며 서비스 관리 원칙은 회사 전체를 개선할 수 있습니다. ITSM은 효율성과 생산성 향상으로 이어집니다. 서비스 관리에 대한 구조화된 접근 방식은 IT 팀을 비즈니스 목표에 정렬하여 예산, 리소스 및 결과에 따라 서비스 제공을 표준화합니다. 비용과 위험을 줄이며 궁극적으로는 고객 경험을 개선합니다. ITSM의 가장 일반적인 이점은 다음과 같습니다. 성공 메트릭을 통해 추적되는 비즈니스 우선 순위에 맞게 IT 팀을 정렬 교차 팀 공동 작업 지원 간소화된 프로젝트 관리 접근 방식을 통해 IT 팀과 개발 팀을 하나로 통합 IT 팀이 지식을 공유하고 지속적으로 개선하도록 역량 강화 더 효율적인 서비스를 위해 요청 조정을 개선 셀프 서비스 및 더 효과적인 프로세스로 고객 중심 촉진 주요 인시던트에 더 빨리 대응하고 향후의 인시던트를 방지 이 모든 것이 비용을 절감하고 더 나은 서비스를 제공할 뿐만 아니라 직원과 고객 만족도를 높여줍니다. ITSM 프로세스 및 서비스 ITIL 4는 최근에 ITSM "프로세스"를 권장하는 것에서 34개의 ITSM "관행"을 도입하는 것으로 바뀌었습니다. 용어를 업데이트한 근거는 "일하는 방식에 대한 전체적인 비전을 얻을 수 있도록 문화, 기술, 정보 및 데이터 관리와 같은 요소를 고려하기 위한 것"입니다. 이러한 포괄적인 접근 방식은 최신 회사의 현실을 더 잘 반영합니다. 여기서는 용어의 차이에 대해 걱정하지 않을 것입니다. 팀이 어떤 프레임워크를 사용하든 관계없이 중요한 사실은 최신 IT 서비스 팀은 리소스를 사용하고 반복 가능한 절차를 따라 일관성 있고 효율적인 서비스를 제공한다는 것입니다. 실제로 관행 또는 프로세스의 활용은 ITSM과 IT를 구별해 주는 요소입니다. 아래에는 핵심 ITSM 프로세스 중 일부가 설명되어 있습니다. 서비스 요청 관리 서비스 요청 관리 는 애플리케이션에 대한 액세스 요청, 소프트웨어 개선 사항 및 하드웨어 업데이트를 포함하여 다양한 고객 서비스 요청을 처리하기 위한 반복 가능한 절차입니다. 서비스 요청 작업 흐름에는 반복적인 요청이 포함되는 경우가 많으며 고객에게 지식을 제공하고 특정 작업을 자동화함으로써 큰 이점을 얻습니다. 지식 관리 지식 관리 는 회사의 지식과 정보를 만들고 공유하고 사용하고 관리하는 프로세스입니다. 지식을 최대한 활용하여 회사의 목표를 달성하기 위한 종합적인 접근 방식을 의미합니다. IT 자산 관리 IT 자산 관리 (ITAM이라고도 함)는 회사의 자산이 적절한 시점에 고려, 배포, 유지 관리 및 업그레이드되고 적절하게 폐기되도록 합니다. 간단히 말해 유형 및 무형의 유용한 항목이 올바르게 추적 및 사용되고 있는지 확인하는 프로세스입니다. 인시던트 관리 인시던트 관리 는 예기치 않은 이벤트 또는 서비스 중단에 대응하고 서비스를 운영 상태로 복원하는 프로세스입니다. 오늘날 기업이 의존하는 모든 소프트웨어 서비스를 고려할 때 잠재적 장애 지점이 그 어느 때보다 많으며, 따라서 이 프로세스는 이슈에 신속하게 대응하고 해결할 준비가 되어 있어야 합니다. 문제 관리 문제 관리 는 IT 서비스 내의 인시던트의 원인을 파악하고 관리하는 프로세스입니다. 문제 관리는 단순히 인시던트를 찾아서 해결하는 것이 아니라 인시던트의 근본 원인을 찾아 이해하고 근본 원인을 제거하는 가장 좋은 방법을 알아내는 것입니다. 변경 관리 변경 관리 는 새로운 서비스 롤아웃, 기존 서비스 관리 또는 코드 문제 해결 등 IT 인프라의 모든 변경 사항을 효율적이고 신속하게 처리하기 위해 표준 절차가 사용되도록 합니다. 효과적인 변경 관리는 병목 현상을 방지하고 위험을 최소화하는 데 필요한 컨텍스트와 가시성을 제공합니다. ITSM 소프트웨어 및 도구 ITSM 소프트웨어 를 통해 IT 팀은 비즈니스 요구 사항에 맞게 정렬하고 변화, 혁신 및 성장에 전략적으로 접근할 수 있습니다. 독립형 애플리케이션부터 플랫폼 서비스까지 시장에서는 다양한 ITSM 소프트웨어 도구가 제공됩니다. Atlassian에서는 IT 팀이 사용하는 기존의 ITSM 시스템과 도구가 유연하지 않아 변화하는 요구 사항에 맞게 사용자 지정하고 적응하기가 어렵다는 불만을 종종 듣습니다. 다양한 ITSM 프로세스마다 다른 도구가 있을 수 있습니다. 모듈식 도구는 장벽을 만들고 최종 사용자를 사일로화하며 팀 전체의 가시성 저하를 유발합니다. 기존의 ITSM 도구는 배포하고 관리하기 어려운 경우가 많으며 최종 사용자가 직관적이지 않은 도구를 채택하게 되어 셀프 서비스 ITSM 기능이 부족하거나 아예 없는 경우가 발생합니다. 서비스 데스크는 강력한 ITSM 솔루션의 기반이므로 비즈니스에 적합한 서비스 데스크 소프트웨어 를 선택하는 것이 중요합니다. 서비스 데스크는 고객과 IT 팀 사이의 인터페이스 역할을 합니다. ITIL 자체에서는 서비스 데스크를 "서비스 공급자와 사용자 간의 단일 연락 지점"으로 정의합니다. 일반적인 서비스 데스크는 인시던트와 서비스 요청을 관리하고 사용자와의 커뮤니케이션도 처리합니다. 서비스 데스크는 다른 ITSM 관행을 관리하는 데도 중요한 역할을 해야 합니다. 서비스 데스크 및 기타 ITSM 도구가 다음과 같은 요구 사항을 충족하는지 생각해 보세요. 간편한 사용 및 설정 : 깔끔하고 직관적인 셀프 서비스 포털이 함께 제공되어 쉽게 도움을 요청하고 참조 자료를 검색하고 이슈에 대한 진행률을 추적할 수 있습니다. 공동 작업 지원 : 개발자와 교차 기능 팀이 더 빠른 이슈 해결을 위해 협업할 수 있는 플랫폼을 제공합니다. 필요에 맞게 조정 : IT 팀이 원하는 문제 해결, 에스컬레이션 또는 변경 프로세스를 지원할 수 있을 정도로 유연합니다. 서비스 데스크 소프트웨어를 선택하는 것은 고객과 IT 팀 간의 인터페이스 역할을 하는 강력한 ITSM 솔루션의 토대를 형성하기 때문에 매우 중요합니다. Jira Service Management 는 사용하기 쉬운 셀프 서비스 포털을 제공하고 팀 간 공동 작업을 지원하고 다양한 IT 문제 해결, 에스컬레이션 및 변경 프로세스를 지원하는 데 필요한 유연성을 제공하여 이러한 문제를 해결하는 솔루션으로 두각을 나타내고 있습니다. 공동 작업 중심의 ITSM 전략으로 가치 제공 가속화 ITSM은 회사 최신화의 중심에 있습니다. 소프트웨어 기반 서비스의 증가 속도가 빨라지면서 IT 서비스 팀은 회사 전체의 직원과 팀이 가치를 더 빠르게 제공하도록 지원하고 있습니다. IT팀의 역할은 비즈니스 지원에서 비즈니스 자체를 적극적으로 차별화하는 것으로 바뀌었습니다. 이제 공동 작업, 사용 편의성, 그리고 더 빠른 가치 전달을 중시하는 ITSM 접근 방식으로 나아가야 할 시기입니다. Jira Service Management 는 ITSM 이니셔티브를 위한 유용한 플랫폼입니다. 7가지 필수 ITSM 관행을 지원할 뿐만 아니라 포괄적인 ITSM 템플릿 도 제공합니다. 이 템플릿은 주요 서비스 관리 워크플로의 구현을 지원하여 ITSM 프로세스를 빠르고 효율적으로 시작할 수 있도록 합니다. 공동 작업 중심의 관행과 원활하게 통합하여 사용 편의성을 강조하는 Jira Service Management는 ITSM 전략을 강화하고 빠른 속도로 가치를 창출하려는 IT 팀을 위한 전략적 도구입니다. 무료로 Jira Service Management 사용해 보기 백서 ITSM을 위한 Atlassian IT 제공, 운영 및 지원 전반에 걸쳐 Atlassian을 활용한 ITSM에 대해 알아야 할 기본 사항과 모범 사례 및 팁을 제공합니다. 가이드 보기 다음 단계 서비스 요청이란 무엇입니까? 서비스 요청 관리를 통해 IT 팀은 고객 요청을 쉽고 빠르게 이행할 수 있습니다. 프로세스 및 모범 사례를 확인하세요. 이 문서 읽기 가입하여 더 많은 기사와 자습서를 보세요. Thank you for subscribing 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#reflect-tunnel-2110485 | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.notion.com/ko/integrations/asana | Asana API 통합 | Notion (노션)에 앱 연결하기 Notion 기능 Notion AI 구축, 작성, 자동화를 위한 툴 에이전트 수동 작업 처리 기업 통합 검색 즉시 답변을 찾을 수 있는 기능 AI 노트 AI가 완벽하게 정리해 드립니다. 문서 간단하면서도 강력한 툴 지식 베이스 모든 지식을 한데 모은 허브 프로젝트 어떤 프로젝트든 관리할 수 있는 툴 사이트 뭐든 빠르게 게시할 수 있는 툴 시작하기 AI 사용 사례 살펴보기 Notion AI로 할 수 있는 작업 보기 마켓플레이스 둘러보기 모든 것을 위한 템플릿 API 통합 보기 Notion에 앱 연결하기 Web Clipper 다운로드 웹에서 가져와 Notion에 저장하세요. 더 빠른 경험을 위한 Notion 데스크톱 앱 다운로드 앱 다운로드 메일 캘린더 AI 대기업 가격 둘러보기 팀 엔지니어링 및 제품 디자인 마케팅 IT 팀 규모 스타트업 중소기업 대기업 교육 학습하기 도움말 센터 Notion 아카데미 고객 스토리 블로그 커뮤니티 파트너 프로그램 만들기 API 템플릿 보안 컨설턴트 영업팀 문의하기 로그인 Notion 무료로 사용하기 ← API 통합 Asana Notion에 추가 Overview Asana는 기업의 업무를 한곳에 체계적으로 정리하여 생산성을 향상해요. 링크 미리보기를 사용하여 Asana 작업을 Notion 페이지에서 바로 확인하거나 데이터베이스 동기화를 사용하여 Asana 프로젝트를 Notion 데이터베이스에 가져오세요. How to use Notion에서 Asana 콘텐츠의 미리보기를 생성하려면 Asana 링크를 Notion에 붙여넣고 미리보기로 붙여넣기 를 선택하세요. 원하는 Notion 페이지에 /asana 를 입력하는 방법도 있어요. 메뉴가 나타나면 링크를 바로 붙여넣으세요. Notion에서 Asana를 처음 사용한다면 API 통합을 승인하라는 프롬프트가 표시될 거예요. 프롬프트를 따라 승인 프로세스를 완료하세요. 승인을 받고 나면 링크의 콘텐츠가 자세한 미리보기로 표시됩니다. Asana의 데이터를 Notion 데이터베이스에 동기화하려면 프로젝트나 작업으로 연결되는 Asana 링크를 복사해서 Notion에 붙여넣고 데이터베이스로 붙여넣기 를 선택하세요. Asana 속성이 추가된 Notion 데이터베이스가 나타나고 작업이 자동으로 채워져요. 이 동기화는 양방향이 아니라는 점에 유의하세요. 가져오기 시점에 Notion에 데이터가 복제되지만 변경 사항은 동기화되지 않아요. Notion의 데이터베이스 동기화에 대해 자세히 알아보세요. Asana의 데이터를 Notion으로 가져오려면 이 가이드를 확인하세요 . 제작자 Notion 카테고리 생산성 공동 작업 기능 링크 미리보기 동기화된 데이터베이스 개발자 링크 웹사이트 이용약관/개인정보 보호 이메일 지원 이슈 신고 여기에 나타나는 모든 제3자 상표(로고 및 아이콘 포함)는 해당 소유자의 자산입니다. Made by Notion으로 특별히 지정된 통합 외의 API 통합은 Notion에서 지원하거나 관리하지 않습니다. API 통합으로 연결되는 제3자 프로덕트 또는 서비스는 비 Notion 애플리케이션(Notion의 MSA(마스터 구독 계약) 또는 개인 이용약관 에 따른 정의)입니다. API 통합을 활성화하거나 Notion API 통합 갤러리를 사용하는 경우, Notion의 API 통합 갤러리 약관에 동의하는 것으로 간주됩니다. . 더 많은 API 통합 PortalWith Create Client Portal with Notion STR Desk Sync Vacation Rental data with Notion in seconds VECTOR AI Your AI Partner Emon Sync Outlook Emails to Notion Notixel Automate your data flow between Notion and Microsoft Excel. neuforms the most affordable typeform alternative to build forms 한국어 쿠키 설정 © 2026 Notion Labs, Inc. 회사 소개 Notion 소개 채용 보안 서비스 상태 이용약관 및 개인정보 보호정책 개인정보 보호 권한 다운로드 iOS & Android Mac & Windows 캘린더 Web Clipper 자료 도움말 센터 요금제 블로그 커뮤니티 API 통합 템플릿 파트너 프로그램 용도별 회사 팀 개인 더 살펴보기 → | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#installation-2110485 | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#reflect-tunnel-2110485 | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://git-scm.com/book/uz/v2/Git-%d0%b4%d0%b0-%d1%82%d0%b0%d1%80%d0%bc%d0%be%d2%9b%d0%bb%d0%b0%d0%bd%d0%b8%d1%88-%d0%98%d1%88-%d0%b6%d0%b0%d1%80%d0%b0%d1%91%d0%bd%d0%bb%d0%b0%d1%80%d0%b8%d0%bd%d0%b8-%d1%82%d0%b0%d1%80%d0%bc%d0%be%d2%9b%d0%bb%d0%b0%d1%88 | Git - Иш жараёнларини тармоқлаш About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Иш бошланиши 1.1 Талқинларни бошқариш ҳақида 1.2 Git нинг қисқача тарихи 1.3 Git асоси 1.4 Командалар сатри 1.5 Git ни ўрнатиш 1.6 Git да биринчи созлашлар 1.7 Қандай ёрдам олиш мумкин? 1.8 Хулосалар 2. Git асослари 2.1 Git омборини яратиш 2.2 Ўзгаришларни омборга ёзиш 2.3 Фиксирлашлар тарихини кўриш 2.4 Ўзгаришларни бекор қилиш 2.5 Узоқ масофадаги омборлар билан ишлаш 2.6 Тамғалаш 2.7 Git да таҳаллуслар 2.8 Хулоса 3. Git да тармоқланиш 3.1 Тармоқланиш ҳақида икки оғиз сўз 3.2 Тармоқланиш ва бирлашиш асослари 3.3 Тармоқларни бошқариш 3.4 Иш жараёнларини тармоқлаш 3.5 Узоқ масофадаги тармоқлар 3.6 Қайта асосланиш 3.7 Хулосалар 4. Git серверда 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.4 Git да тармоқланиш - Иш жараёнларини тармоқлаш Иш жараёнларини тармоқлаш Энди сиз тармоқланиш асосларини, тармоқланишдаги бирлаштиришларни биласиз. Бироқ улар билан нима қилиш мумкин? Ушбу бўлимда биз унчалик аҳамиятга эга бўлмасада сизни ўзингизни яратувчанлик циклларингизда қўллашингиз мумкин бўлган ҳолат яъни иш жараёнини тармоқлаш имконияти ҳақида гаплашамиз. Узоқ давом этувчи тармоқланиш Шунинг учун ҳам Git оддий 3 томонламали бирлаштиришни қўллайди. Узоқ вақт этган тармоқланишдаги бир тармоқдан иккинчи тармоққа бир неча бор бирлаштиришни умуман онсонгина бажарилади. Бу шуни англатадики сиз яратувчанлик билан шуғулланаётган вақтингиз давомида бир нечта тармоққа эга бўлиб улардан фойдаланган ҳолда турли хил тайёр соҳаларни (stage) яратишингиз мумкин бўлади. Сиз қоидага мос ҳолда улардан баъзиларини бошқаларига бирлаштириш учун фойдаланишингиз мумкин бўлади. Кўпгина Git да ишловчи яратувчилар деярли йўлга қўйиш учун тайёр бўлган ёки йўлга қўйилаётган ишчи соҳа master тармоққа эга бўлишади. Улар бошқа параллел бўлган develop ёки next дея номланадиган тармоқни яратиб олишади. Унда улар ишлашади ёки лойиҳани йўлга қўйишга тайёрлигини тест қилишади. У ҳар доим ҳам йўлга қўйишга тайёр бўлмайди. Аммо уни йўлга қўйиш учун ўтказилган тест муваффиқиятли ўтганда master тармоққа бирлаштириш мумкин бўлади. Бу, тармоқлар (қисқа-яшаган тармоқлар сизни аввалги iss53 тармоғингизга ўхшайди) мавзусида улар тайёр бўлганида олиш (pull) учун ишлатилган эди, уларни ишонч билан яратиш жуда кўп тестларни ўтказишга имкон беради ва хатоликларни (bug) келиб чиқишини олдини олади. Ҳақиқатда биз сиз яратган фиксирлашларни кўрсаткичларини силжитиш ҳақида гаплашдик. The stable branches are farther down the line in your commit history, and the bleeding-edge branches are farther up the history. Figure 26. A linear view of progressive-stability branching It’s generally easier to think about them as work silos, where sets of commits graduate to a more stable silo when they’re fully tested. Figure 27. A “silo” view of progressive-stability branching You can keep doing this for several levels of stability. Some larger projects also have a proposed or pu (proposed updates) branch that has integrated branches that may not be ready to go into the next or master branch. The idea is that your branches are at various levels of stability; when they reach a more stable level, they’re merged into the branch above them. Again, having multiple long-running branches isn’t necessary, but it’s often helpful, especially when you’re dealing with very large or complex projects. Topic Branches Topic branches, however, are useful in projects of any size. A topic branch is a short-lived branch that you create and use for a single particular feature or related work. This is something you’ve likely never done with a VCS before because it’s generally too expensive to create and merge branches. But in Git it’s common to create, work on, merge, and delete branches several times a day. You saw this in the last section with the iss53 and hotfix branches you created. You did a few commits on them and deleted them directly after merging them into your main branch. This technique allows you to context-switch quickly and completely – because your work is separated into silos where all the changes in that branch have to do with that topic, it’s easier to see what has happened during code review and such. You can keep the changes there for minutes, days, or months, and merge them in when they’re ready, regardless of the order in which they were created or worked on. Consider an example of doing some work (on master ), branching off for an issue ( iss91 ), working on it for a bit, branching off the second branch to try another way of handling the same thing ( iss91v2 ), going back to your master branch and working there for a while, and then branching off there to do some work that you’re not sure is a good idea ( dumbidea branch). Your commit history will look something like this: Figure 28. Multiple topic branches Now, let’s say you decide you like the second solution to your issue best ( iss91v2 ); and you showed the dumbidea branch to your coworkers, and it turns out to be genius. You can throw away the original iss91 branch (losing commits C5 and C6 ) and merge in the other two. Your history then looks like this: Figure 29. History after merging dumbidea and iss91v2 We will go into more detail about the various possible workflows for your Git project in Distributed Git , so before you decide which branching scheme your next project will use, be sure to read that chapter. It’s important to remember when you’re doing all this that these branches are completely local. When you’re branching and merging, everything is being done only in your Git repository – no server communication is happening. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:43 |
https://www.atlassian.com/ru/software/jira/service-management/enterprise#content | Jira Service Management Enterprise (версия Cloud) | Atlassian Перейти к содержанию Возможности Цены Решения По примеру использования Служба ИТ-поддержки ИТ-операции Бизнес-команды Служба поддержки клиентов Отдел кадров По возможностям Небольшие команды Premium Enterprise По отрасли Технологии и телекоммуникации Финансовые услуги Розничная торговля Производство Ресурсы По типу ITSM Руководство Дополнительные ресурсы Больше + Получить бесплатно Получить бесплатно Назад Получить бесплатно Возможности Цены Решения Ресурсы Войти По примеру использования Служба ИТ-поддержки ИТ-операции Бизнес-команды Служба поддержки клиентов Отдел кадров По возможностям Небольшие команды Premium Enterprise По отрасли Технологии и телекоммуникации Финансовые услуги Розничная торговля Производство По типу ITSM Руководство Дополнительные ресурсы Получить бесплатно Возможности Цены Решения Ресурсы Войти По примеру использования Служба ИТ-поддержки ИТ-операции Бизнес-команды Служба поддержки клиентов Отдел кадров По возможностям Небольшие команды Premium Enterprise По отрасли Технологии и телекоммуникации Финансовые услуги Розничная торговля Производство По типу ITSM Руководство Дополнительные ресурсы Теперь сервис Jira Service Management входит в Service Collection, что многократно повышает эффективность этого решения. Откройте для себя исключительные возможности с Rovo, активами и новым приложением Customer Service Management. Попробовать Выведите Jira Service Management на новый уровень Jira Service Management Enterprise — наш самый продвинутый тарифный план Cloud, поддерживающий безопасную и эффективную командную работу при любом масштабе. Связаться с отделом продаж Корпоративному масштабу — корпоративные возможности Обеспечьте расширенную безопасность, масштабируемость, аналитику и соответствие требованиям с помощью Jira Service Management Enterprise. Безопасность Масштаб Аналитика Соответствие требованиям Облегчите аутентификацию пользователей Централизуйте визуализацию, аудиты и управление идентификацией и доступом с помощью Guard Standard. Управляйте пользователями централизованно Подключите несколько поставщиков учетных данных для автоматизированного управления пользователями из разных отделов и регионов. Покончите с теневыми ИТ-ресурсами Используйте функцию запросов приложений для просмотра и подтверждения запросов на новые сайты. Все возможности и цены Ресурсы Узнайте об Atlassian Guard Посмотрите, как Guard помогает централизовать безопасность и прозрачность в облаке Atlassian. Подробнее Посмотрите на безопасность Cloud Enterprise в действии Узнайте, как снизить риски с помощью средств управления безопасностью в Cloud Enterprise. Смотреть вебинар Ознакомьтесь с Cloud Enterprise Откройте для себя такие возможности Cloud Enterprise, как контроль теневых ИТ-ресурсов. Смотреть демонстрацию Оптимизируйте растущее потребление Настраивайте сайты для новых команд и отделов, не затрагивая другие рабочие процессы. Легко управляйте своей организацией Используйте централизованное администрирование и выставление счетов для управления пользователями и продуктами. Платите за каждого пользователя каждого продукта один раз. Усовершенствуйте процесс управления изменениями Используйте несколько «песочниц» на сайте, чтобы управлять изменениями и выполнять параллельное тестирование в безопасности и в соответствии с отраслевыми стандартами. Все возможности и цены Ресурсы Подробнее о Cloud Enterprise Узнайте, как Cloud Enterprise помогает организациям масштабироваться. Загрузить руководство Изучите многосайтовую архитектуру Узнайте, как клиенты используют несколько сайтов для обеспечения гибкости и контроля. Загрузить электронную книгу Посмотрите на администрирование Atlassian в действии Посмотрите демонстрацию управления масштабом в Cloud Enterprise. Смотреть демонстрацию Объедините данные в своем пакете инструментов Объедините данные основных и сторонних разработчиков в Atlassian Data Lake. Принимайте решения на основе данных Отслеживайте показатели в управлении изменениями, инцидентами и запросами, чтобы устранить блокеры служб с помощью аналитики на основе ИИ. Повысьте эффективность данных в Jira Service Management Добавьте данные Atlassian в свою собственную среду или инструменты бизнес-аналитики. Все возможности и цены Ресурсы Ускорьте принятие масштабных решений Визуализируйте данные с помощью готовых шаблонов и настраиваемого анализа данных. Подробнее Посмотрите, как DISH Network выигрывает благодаря Cloud Enterprise Узнайте, как команды, похожие на вашу, создают ценность с помощью Atlassian Analytics. Посмотрите запись Узнайте, как вывести принятие решений на новый уровень Получайте полезную аналитику, совершенствуйте совместную работу и добивайтесь целей с Atlassian Analytics. Смотреть вебинар Ориентируйтесь в глобальной среде соответствия требованиям Уверенно выходите на новые рынки с региональными и отраслевыми стандартами соответствия требованиям. Все возможности и цены Ресурсы Погрузитесь глубже в Cloud Enterprise Узнайте больше о том, что делает Cloud Enterprise уникальным решением. Загрузить руководство Посетите Atlassian Trust Center Ознакомьтесь с подходом Atlassian к соблюдению нормативных требований. Подробнее Узнайте, почему компания Finoa выбрала Cloud Enterprise Читайте, как в Finoa соблюдают стандарты соответствия требованиям с помощью Cloud Enterprise. Подробнее Не простаивайте ни секунды благодаря расширенной поддержке Старшие агенты поддержки Круглосуточная поддержка Поддержка по телефону Время ответа 30 минут для критических проблем Нам доверяют более 80 % компаний из списка Fortune 500 Ознакомиться с историями клиентов “ Автоматические уведомления, мониторинг SLA и заблаговременные оповещения в Jira Service Management помогают Riverty предоставлять клиентам лучшую поддержку. ” Andrei Tuch Владелец продукта Atlassian Прочтите историю Riverty “ Мы обнаружили, что можем экономить на инструментах 2,5 млн долл. США в год за счет централизации в Atlassian Cloud и более эффективного управления. Это означает снижение затрат на 36 % в год. Для этого понадобилось бы устранить дублирование рабочих мест в рамках лицензий на инструменты [и] тщательнее организовать управление. ” Emily Novak Менеджер по продукту, отдел развития цифровых рабочих пространств и решений Прочтите историю Rivian “ Благодаря возможности создавать несколько сайтов без дополнительных затрат мы можем разделять данные исходя из соображений безопасности и приспосабливать одно и то же решение под несколько сценариев использования. Это полностью укладывается в наше представление о единообразном ландшафте приложений. ” Radoslav Danchev Вице-президент по совместной работе, рабочему пространству и поддержке Прочтите историю Software AG Нужна повышенная безопасность? Atlassian Guard Premium дает дополнительный уровень безопасности: предотвращайте угрозы до того, как они станут инцидентами. Подробнее об Atlassian Guard Premium НЕ ГОТОВЫ К ENTERPRISE? Jira Service Management Premium поддерживает управление активами, расширенное управление инцидентами и множество других возможностей без масштабирования и контроля уровня Enterprise. Подробнее о плане Premium Укрепите свое конкурентное преимущество с помощью Jira Service Management Enterprise Связаться с отделом продаж Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Обратная связь Продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы корпоративного уровня Смотреть все ресурсы Copyright © 2026 Atlassian Политика конфиденциальности Уведомление о сборе персональных данных Условия использования Импрессум русский ▾ | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/manage-tests#content-wrapper | Manage Tests | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Manage Tests Understand and control the execution of your automated Reflect tests. In This Section View Test Run A single view for examining a test run, as well as inspecting and modifying a test. Editing / Re-Recording Configure the assertions and validations in your test, and modify test steps directly in-line. Folders Group related tests together in lightweight collections. Suites Orchestrate regression test plans by combining test cases, configurations, and notifications. In this section : Manage Tests In This Section Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/manage-tests.html#in-this-section-2110463 | Manage Tests | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Manage Tests Understand and control the execution of your automated Reflect tests. In This Section View Test Run A single view for examining a test run, as well as inspecting and modifying a test. Editing / Re-Recording Configure the assertions and validations in your test, and modify test steps directly in-line. Folders Group related tests together in lightweight collections. Suites Orchestrate regression test plans by combining test cases, configurations, and notifications. In this section : Manage Tests In This Section Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.atlassian.com/es/software/compass/pricing | Compass: precios | Atlassian Saltar al contenido Funciones Precios Más + Consíguelo gratis Consíguelo gratis Atrás Consíguelo gratis Funciones Precios Iniciar sesión Consíguelo gratis Funciones Precios Iniciar sesión Escala tu plataforma interna para desarrolladores con precios simples y transparentes Tamaño de equipo: usuarios Facturar: Mensualmente Anualmente AHORRA HASTA UN 17 % Free Para equipos pequeños que quieran poner en marcha su plataforma interna para desarrolladores $0 Consíguelo ahora Incluye: Hasta 3 usuarios completos, usuarios básicos ilimitados Los usuarios completos son usuarios de pago y facturables de Compass que tienen acceso a todas las funciones disponibles en el plan de su sitio. Los usuarios básicos necesitan una cuenta de Atlassian gratuita. Tienen acceso a un conjunto básico de funciones incluidas para el rol de usuario básico, independientemente del plan de su sitio. Catálogo de componentes de software con servicios ilimitados Cataloga los componentes de software de tu organización y reúne la información y los equipos dispersos en un solo lugar. Navega a través de tu arquitectura de software, supervisa tus componentes y las relaciones entre ellos, los equipos que los poseen y las herramientas y prácticas que impulsan esos componentes, no solo para mantenerlos en funcionamiento, sino también para mejorarlos. Cuadros de mando y métricas de estado Supervisa las métricas del estado del software y aplica cuadros de mandos de seguridad y estado para mejorar la experiencia de desarrollador. 3 campos personalizados y cuadros de mandos Personaliza los cuadros de mandos (criterios aplicados a un componente para medir su estado) Aplicaciones e integraciones Integra Compass con otras aplicaciones que ya utilices. Obtén más información . Standard Para equipos en crecimiento que quieran mejorar su experiencia de desarrollo y su preparación operativa $7.67 por usuario al mes Iniciar la versión de prueba gratuita Todas las funciones de Free, y además: Hasta 35 000 usuarios completos y usuarios básicos ilimitados Los usuarios completos son usuarios de pago y facturables de Compass que tienen acceso a todas las funciones disponibles en el plan de su sitio. Los usuarios básicos necesitan una cuenta de Atlassian gratuita. Tienen acceso a un conjunto básico de funciones incluidas para el rol de usuario básico, independientemente del plan de su sitio. 3 tipos de componentes personalizados, 50 campos y cuadros de mando personalizados, 100 métricas personalizadas Describe y clasifica los componentes, personaliza los cuadros de mandos (criterios que se aplican a un componente para medir su estado) y crea nuevas métricas que se adapten a las necesidades de tu equipo. Operaciones Gestiona los horarios de guardia y responde a las alertas de más de 150 integraciones; todo ello dentro de Compass. Enruta las alertas por componente afectado y obtén una resolución más rápida con información rica en contexto de tu completo catálogo de software. Un año de retención de datos Accede a los datos de tu cadena de herramientas en Compass durante un periodo de hasta un año. Esto incluye las métricas, los eventos y las puntuaciones del cuadro de mandos. Los datos del catálogo son ilimitados. Soporte local 9 horas al día, 5 días a la semana Tiempo de respuesta de 2 horas para las incidencias críticas por parte del equipo de soporte de Cloud. Recomendado Premium Para organizaciones grandes que busquen escalar su IDP con funciones avanzadas de cumplimiento, soporte y datos $23.96 por usuario al mes Iniciar la versión de prueba gratuita Todas las funciones de Standard, y además: Hasta 35 000 usuarios completos y usuarios básicos ilimitados Los usuarios completos son usuarios de pago y facturables de Compass que tienen acceso a todas las funciones disponibles en el plan de su sitio. Los usuarios básicos necesitan una cuenta de Atlassian gratuita. Tienen acceso a un conjunto básico de funciones incluidas para el rol de usuario básico, independientemente del plan de su sitio. 14 tipos de componentes personalizados, 100 campos y cuadros de mando personalizados, 200 métricas personalizadas Describe y clasifica los componentes, personaliza los cuadros de mandos (criterios que se aplican a un componente para medir su estado) y crea nuevas métricas que se adapten a las necesidades de tu equipo. Operaciones mejoradas Políticas avanzadas de integraciones y escalación, políticas de alertas y notificaciones, notificaciones de voz y supervisión con Heartbeats de tus herramientas de observación. Dos años de retención de datos Accede a los datos de tu cadena de herramientas en Compass durante un periodo de hasta un año. Esto incluye las métricas, los eventos y las puntuaciones del cuadro de mandos. Los datos del catálogo son ilimitados. SLA con un 99,9 % de tiempo de actividad SLA con un tiempo de actividad del 99,9 % de forma ininterrumpida, respaldado financieramente con créditos de nivel de servicio. Soporte ininterrumpido para incidencias críticas Tiempo de respuesta de 1 hora para las incidencias críticas por parte del equipo de soporte de Cloud. Listas de aceptación de IP Refuerza la seguridad del equipo limitando el acceso a tu sitio a intervalos IP de confianza. Permisos Mantén la integridad de tu catálogo de componentes a gran escala al restringir el acceso a las acciones críticas solo a quienes las necesitan. Comparar funciones Free Standard Premium Usuarios Límite de usuarios completos por sitio Este es el número máximo de usuarios completos que puedes añadir a tu sitio de Compass (se te proporciona un sitio por plan). Los usuarios completos son usuarios con licencia que tienen acceso a todas las funciones incluidas en el plan de su sitio de Compass. Consulta la lista completa de permisos de creador. Free Tres usuarios completos Standard 35 000 usuarios completos Premium 35 000 usuarios completos Número de usuarios básicos Los usuarios básicos necesitan una cuenta de Atlassian gratuita. Tienen acceso a un conjunto básico de funciones incluidas en la lista para su rol, independientemente del plan de su sitio de Compass. Consulta la lista completa de permisos de creador. Free Ilimitado Standard Ilimitado Premium Ilimitado Catálogo Creación de componentes Empieza a crear tu catálogo de software creando los componentes de forma manual mediante la API o importándolos desde las herramientas conectadas de tu cadena de herramientas. Free checked Standard checked Premium checked Gestión de la propiedad de los componentes Fomenta la responsabilidad y facilita la comunicación asignando equipos propietarios a los componentes. Aprende a gestionar la propiedad de los componentes. Free checked Standard checked Premium checked Tipos de componentes personalizados Configura el catálogo para satisfacer las necesidades exactas de tu organización. Free Ninguno Standard Tres Premium 14 fuente de actividades Obtén los eventos de los componentes de tu cadena de herramientas en tiempo real y supervísalos a lo largo del tiempo. Más información sobre el feed de actividades. Free checked Standard checked Premium checked Dependencias Define las relaciones entre los componentes e identifica su impacto mutuo. Obtén más información sobre las dependencias . Free checked Standard checked Premium checked Configuración como código Gestiona y actualiza los componentes desde un archivo de configuración YAML junto con tu código. Más información sobre la configuración como código. Free checked Standard checked Premium checked Anuncios Comparte las próximas noticias o cambios y mantente al día de los anuncios que puedan afectar a tus componentes. Más información sobre los anuncios. Free checked Standard checked Premium checked Permisos Las políticas de permisos te ayudan a mantener la integridad de tu catálogo de componentes a gran escala al restringir el acceso a las acciones críticas solo a quienes las necesitan. Free Standard Premium checked Operaciones Gestión de guardias y alertas Alertas y planificación de guardias fluidas en una interfaz unificada. Menos cambios de contexto con alertas junto con tu catálogo de componentes. Recibe notificaciones a través de una variedad de opciones de notificación, como correo electrónico, SMS y aplicación móvil. Free Standard checked Premium checked Retención de datos de alertas Duración durante la cual tus datos de alerta permanecerán en el sistema antes de su eliminación automática. Free 1 mes Standard 1 año Premium 3 años Supervisión e integraciones con Slack Utiliza una integración con la herramienta de supervisión u observación que elijas, con más de 150 integraciones, y ofrece a tus ingenieros una amplia variedad de opciones de notificación, como correo electrónico, SMS, aplicación móvil y Slack. Free Standard checked Premium checked Políticas de alertas y notificaciones Modifica automáticamente las alertas y añade información a medida que se crean. Establece políticas para todo el equipo para retrasar o suprimir las notificaciones por tipo de alerta. Free Standard Premium checked Informes de alertas Accede a los informes históricos de alertas y notificaciones e identifica las áreas de éxito y las oportunidades de mejora. Obtén información sobre tus SLA y cómo se distribuyen las cargas de trabajo de guardia. Free Standard Premium checked Configuraciones avanzadas Notificaciones de voz, roles personalizados, notificaciones basadas en rol, sincronización con incidencias de Jira y supervisión con Heartbeats de tus herramientas de observación. Free Standard Premium checked Aplicaciones Aplicaciones propias y de terceros Conecta fácilmente Compass con las herramientas que usas a diario. Te permite personalizar la interfaz de usuario del producto y desarrollar nuevas funciones a nivel de componentes, equipos o de toda la empresa. Free checked Standard checked Premium checked Aplicaciones de Atlassian Marketplace El Atlassian Marketplace es una plataforma para que los clientes de Atlassian descubran, prueben y compren aplicaciones para los productos de Atlassian. Puedes usar las aplicaciones para personalizar y ampliar tu producto de Atlassian. El Marketplace ofrece aplicaciones desarrolladas tanto por Atlassian como por terceros. Más información Free checked Standard checked Premium checked Equipos y salud Gestión de equipos Crea y descubre equipos en toda tu arquitectura distribuida de software. Asigna responsabilidades a la creación, el mantenimiento y el funcionamiento de los componentes y fomenta las prácticas recomendadas que crean un software excelente. Más información sobre cómo usar a los equipos en Compass. Free checked Standard checked Premium checked Panel de equipo Encuentra la información de tu equipo, consulta y gestiona la propiedad de los componentes y desempeña las funciones relacionadas con el equipo desde un panel del equipo centralizado. Más información sobre los paneles del equipo. Free checked Standard checked Premium checked Métricas predefinidas Recopila puntos de datos que te ayuden a supervisar y evaluar el rendimiento de tus procesos, productos y equipos con las métricas . Usa nuestras métricas predefinidas para influir en tus prácticas de DevOps y mejorarlas. Free checked Standard checked Premium checked Cuadros de mando Codifica las prácticas recomendadas de desarrollo y operaciones a gran escala. Da autonomía a los equipos a la vez que te aseguras de que se mantengan las prácticas recomendadas de seguridad, conformidad y fiabilidad. Da tus primeros pasos respecto al estado con la ayuda de nuestros cuadros de mandos integrados. Más información sobre los cuadros de mandos. Free Tres Standard 50 Premium 100 Métricas personalizadas Crea métricas personalizadas para supervisar y evaluar el rendimiento de tus procesos, productos y equipos con datos que sean valiosos para ti. Free Tres Standard 100 Premium 200 Almacenamiento y soporte Soporte El plan Free ofrece acceso a los recursos de autoayuda de la Comunidad de Atlassian, mientras que el plan Standard incluye soporte en horario laboral ( consulta qué horarios se aplican a tu zona horaria ). Más información sobre el soporte. Free Comunidad de Atlassian Standard Soporte en horario comercial local Premium Soporte Premium ininterrumpido Almacenamiento Accede a los datos de tu cadena de herramientas en Compass durante un período de tiempo determinado. Esto incluye las métricas, los eventos y las puntuaciones del cuadro de mandos, mientras que los datos del catálogo son ilimitados en ambos planes. Free Standard Un año de retención de datos Premium Un mes de retención de datos SLA Free Standard Premium 99,9 % Controles del administrador Listas de aceptación de IP Refuerza la seguridad del equipo limitando el acceso a tu sitio a intervalos IP de confianza. Free Standard Premium checked Atlassian Guard Standard (SSO, SCIM, sincronización con Active Directory) Inicio de sesión único obligatorio, seguridad de usuarios externos, gestión de aplicaciones móviles, información de la organización, registros de auditoría iniciados por el administrador. Free Requiere una suscripción a Atlassian Guard Standard Standard Requiere una suscripción a Atlassian Guard Standard Premium Requiere una suscripción a Atlassian Guard Standard Protege tus datos imprescindibles Añade Atlassian Guard para mejorar la seguridad y la visibilidad de tus productos de Atlassian Cloud. Establece políticas de seguridad proactivas, detecta rápidamente las conductas sospechosas y toma medidas con los pasos de corrección sugeridos para proteger tu trabajo más valioso. Además, con un plan Cloud Enterprise, tienes soporte para varios proveedores de identidades (IDP) y Atlassian Guard Standard. Learn more Obtén más información Definiciones de usuario completo y usuario básico Los usuarios completos son usuarios de pago y facturables de Compass que tienen acceso a todas las funciones disponibles en el plan de su sitio. Los usuarios básicos necesitan una cuenta de Atlassian gratuita. Tienen acceso a un conjunto básico de funciones incluidas para el rol de usuario básico, independientemente del plan de su sitio. Consulta el desglose completo de los permisos que tiene cada rol en Compass. Definición de administrador del producto Los administradores de productos son usuarios completos (es decir, usuarios facturables y de pago) de Compass. Tienen acceso a todas las funciones disponibles en el plan de su sitio, además de funciones administrativas adicionales, como la instalación y la configuración de aplicaciones. Integraciones con otros productos de Atlassian Los planes Free y Standard incluyen integraciones con los siguientes productos de Atlassian: Jira, Jira Service Management, Bitbucket y Opsgenie. Jira: descubre y crea tu catálogo de software importando componentes de los repositorios vinculados a Jira. Vincula los componentes con las incidencias de Jira para supervisar, priorizar y completar el trabajo correcto en tu arquitectura de software. Jira Service Management: descubre y crea tu catálogo de software importando servicios de Jira Service Management como componentes de Compass. Obtén una visión holística de tu servicio y realiza investigaciones de incidentes significativas vinculando los registros de servicios de Jira Service Management y Compass. Bitbucket: descubre y crea tu catálogo de software importando componentes de los repositorios. Automatiza la gestión de los componentes desde herramientas externas con la configuración como código. Consulta los datos de los componentes de tu cadena de herramientas en una ubicación unificada de Compass. Más información sobre la integración de Jira con Bitbucket Cloud. Opsgenie : Consulta la información de guardia de tu componente y visualiza los eventos y las métricas de los incidentes en un lugar unificado en Compass. Más información sobre la integración con Opsgenie. Planes de suscripción y periodo de versión de prueba gratuita El plan Free permite hasta un número ilimitado de usuarios básicos por sitio y hasta tres usuarios completos de forma gratuita, sin necesidad de tarjeta de crédito. Si quieres añadir más de tres usuarios completos u obtener acceso a más funciones, soporte y almacenamiento, puedes apuntarte a una versión de prueba gratuita de 14 días de nuestro plan Standard o cambiarte a él en la sección "Gestionar suscripción" de tu sitio. No se requiere información de pago durante la versión de prueba gratuita de 14 días. No se requiere ninguna información de pago hasta tu primer pago. Puedes cancelar cuando quieras. Durante la versión de prueba gratuita, te enviaremos recordatorios para actualizar tus detalles de pago y que no haya interrupciones del servicio, pero también puedes cambiar al plan Free por tu cuenta. Si no te convence tu compra, ofrecemos una garantía de reembolso durante 30 días. Información de pago Puedes pagar tu suscripción con tarjeta de crédito (MasterCard, Visa o American Express). En este momento, las suscripciones a Compass solo son mensuales, aunque tenemos previsto ofrecer suscripciones anuales en el futuro. Por ahora, solo aceptamos pagos de Compass en dólares estadounidenses. Tenemos pensado aceptar otras monedas en el futuro. Acerca de las opciones de Cloud y autogestionadas Compass solo está disponible en Cloud , lo que significa que no ofrecemos opciones de Data Center con tu suscripción. Cómo invitar a los usuarios Los administradores del sitio pueden activar Compass para todos los usuarios. Cuando Compass esté activo, todos los usuarios de tu sitio pueden acceder a Compass con el Intercambiador de aplicaciones. Más información sobre cómo invitar a los usuarios a Compass. Compañía Oportunidades profesionales Eventos Blogs Relaciones con los inversores Atlassian Foundation Kit de prensa Contacto Productos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos los productos Recursos Servicio técnico Compras y licencias Comunidad de Atlassian Base de conocimientos Marketplace Mi cuenta Crear ticket de asistencia Tutorial Partners Formación y certificación Documentación Recursos para desarrolladores Servicios empresariales Ver todos los recursos Copyright © 2026 Atlassian Política de privacidad Aviso de recopilación de datos Términos Aviso legal Español ▾ window.SSR_detailMetrics=Object.freeze({"getFeatureGateValues":{"startTime":0,"duration":55},"fetchUserLocaleS2S":{"startTime":322,"duration":363},"initializeFeatureGatesClient":{"startTime":318,"duration":4},"resolveRoute":{"startTime":322,"duration":371},"contentful-getCCPPricingData":{"startTime":694,"duration":5},"resolvePageProps":{"startTime":693,"duration":1653},"render":{"startTime":2352,"duration":81}}); window.SSR_totalMetrics=Object.freeze({"startTime":1768296577026,"duration":2433}); window.SSR_region="ap-northeast-2"; window.SSR_languagePack={"UserSeg.teamTypeSelection.customerService":"Atención al cliente","UserSeg.teamTypeSelection.dataScience":"Ciencia de datos","UserSeg.teamTypeSelection.design":"Diseño","UserSeg.teamTypeSelection.finance":"Finanzas","UserSeg.teamTypeSelection.humanResources":"Recursos humanos","UserSeg.teamTypeSelection.itSupport":"Soporte de TI","UserSeg.teamTypeSelection.legal":"Jurídico","UserSeg.teamTypeSelection.marketing":"Marketing","UserSeg.teamTypeSelection.operations":"Operaciones","UserSeg.teamTypeSelection.otherOrPersonal":"Otros","UserSeg.teamTypeSelection.productManagement":"Gestión de productos","UserSeg.teamTypeSelection.projectManagement":"Gestión de proyectos","UserSeg.teamTypeSelection.sales":"Ventas","UserSeg.teamTypeSelection.softwareDevelopment":"Desarrollo de software","Jtbd.adhocTask":"Gestión ad hoc de tareas e incidentes","Jtbd.backButton":"Atrás","Jtbd.chooseOptions":"Elige hasta tres opciones","Jtbd.continueButton":"Continuar","Jtbd.createStrategies":"Crea estrategias y objetivos","Jtbd.documentation":"Documentación centralizada","Jtbd.header":"¿Cómo planea tu equipo usar Jira?","Jtbd.launchCampaigns":"Lanza campañas","Jtbd.manageBudget":"Gestiona los recursos y los presupuestos","Jtbd.manageClient":"Gestión de las relaciones con clientes y vendedores","Jtbd.manageMarketing":"Gestiona el contenido de marketing","Jtbd.manageTasks":"Gestiona las tareas","Jtbd.mapDependencies":"Asigna las dependencias de trabajo","Jtbd.prioritizeWork":"Prioriza el trabajo","Jtbd.processRequests":"Procesa las solicitudes de las partes interesadas","Jtbd.projectPlanning":"Planificación y coordinación de proyectos","Jtbd.reportProgress":"Informa sobre el progreso del proyecto","Jtbd.riskCompliance":"Cumplimiento y gestión de riesgos","Jtbd.runSprints":"Ejecutar sprints","Jtbd.subHeader":"Tus elecciones no limitarán lo que puedes hacer.","Jtbd.systemAudits":"Evaluaciones de sistemas y herramientas","Jtbd.trackBugs":"Supervisa los errores","Jtbd.workInScrum":"Trabajar en scrum","TransparentTemplateV2.itSupport.productManagement.additionalInfo":"Se te redirigirá a Jira Product Discovery. Seguirás teniendo acceso a Jira en tu sitio.","TransparentTemplateV2.itSupport.productManagement.poweredByText":"Al seleccionar \"Continuar\", aceptas el {customerAgreementLink} y la {privacyPolicyLink}.","TransparentTemplateV2.itSupport.serviceManagement.additionalInfo":"Se te redirigirá a {productName} y se te aprovisionará a Service Collection. Seguirás teniendo acceso a Jira en tu sitio.","TransparentTemplateV2.itSupport.serviceManagement.customerAgreementLink":"Acuerdo de cliente de Atlassian","TransparentTemplateV2.itSupport.serviceManagement.legalNotice":"Al seleccionar esta plantilla, aceptas el {customerAgreementLink} y la {privacyPolicyLink}.","TransparentTemplateV2.itSupport.serviceManagement.poweredByText":"Con tecnología de","TransparentTemplateV2.itSupport.serviceManagement.privacyPolicyLink":"Política de privacidad de Atlassian","sample-project.utils.approved-column-name":"Aprobado","sample-project.utils.asset-issue-type-name":"Activo","sample-project.utils.bug-issue-type-name":"Error","sample-project.utils.campaign-issue-type-name":"CAMPAÑA","sample-project.utils.candidate-issue-type-name":"Aspirante","sample-project.utils.contact-issue-type-name":"Contacto","sample-project.utils.default-kanban-project-name":"Mi proyecto de Kanban","sample-project.utils.default-scrum-project-name":"Mi proyecto de scrum","sample-project.utils.done-column-name":"Finalizado","sample-project.utils.feature-issue-type-name":"Función","sample-project.utils.idea-column-name":"Idea","sample-project.utils.in-design-column-name":"En Diseño","sample-project.utils.in-progress-column-name":"En curso","sample-project.utils.in-review-column-name":"En revisión","sample-project.utils.incident-issue-type-name":"Incidente","sample-project.utils.live-column-name":"En Vivo","sample-project.utils.request-issue-type-name":"Solicitud","sample-project.utils.research-item-issue-type-name":"Elemento de investigación","sample-project.utils.resolved-column-name":"RESUELTO","sample-project.utils.service-request-issue-type-name":"Solicitud de servicio","sample-project.utils.story-issue-type-name":"Historia","sample-project.utils.support-issue-type-name":"Soporte","sample-project.utils.task-issue-type-name":"Tarea","sample-project.utils.testing-column-name":"Pruebas","sample-project.utils.todo-column-name":"Por hacer","sample-project.utils.user-testing-column-name":"UserTesting","sample-project.utils.waiting-for-customer-column-name":"ESPERANDO AL CLIENTE","ConfluenceTemplatesCategoryDetailPage.pageTitle":"Plantillas de {title} gratuitas | Confluence","ConfluenceTemplatesCollectionDetailPage.pageTitle":"Colección {title} gratuita | Confluence","ConfluenceTemplatesCollectionDetailPage.title-suffix":"Colección | Atlassian","Wac.Signup.PostOrder.Org.Setup.empty.page.administrationButton":"Ir a Administración de Atlassian","Wac.Signup.PostOrder.Org.Setup.empty.page.header":"No hay ninguna organización apta para aprovisionar tu pedido.","Wac.Signup.PostOrder.Org.Setup.empty.page.introBody":"Consulta tus organizaciones actuales en Administración de Atlassian.","Wac.Signup.PostOrder.Org.Setup.empty.page.introBodyDescription":"Es posible que todas tus organizaciones ya tengan los productos o que tengas que iniciar sesión con otra cuenta que tenga permisos de aprovisionamiento.","Wac.Signup.PostOrder.CustomerManagedKeys.organization.card.alreadyEnabledCustomerManagedKeys":"Esta organización ya tiene claves gestionadas por el cliente","Wac.Signup.PostOrder.Guard.organization.card.alreadyEnabledGuard":"Esta organización ya tiene Guard","Wac.Signup.PostOrder.Rovo.organization.card.alreadyEnabledRovo":"Esta organización ya tiene Rovo","Wac.Signup.PostOrder.Rovo.organization.card.select":"Seleccionar","Wac.Signup.PostOrder.ServiceCollection.organization.card.alreadyEnabledServiceCollection":"Esta organización ya tiene Service Collection","Wac.Signup.PostOrder.Strategy.organization.card.alreadyEnabledStrategy":"Esta organización ya tiene Strategy","Wac.Signup.PostOrder.Twc.organization.card.alreadyEnabledTwc":"Esta organización ya tiene Twc","Wac.Signup.PostOrder.CustomerManagedKeys.organization.page.subtitle":"Selecciona una organización existente e inicia las claves gestionadas por el cliente.","Wac.Signup.PostOrder.Guard.organization.page.subtitle":"Selecciona una organización e inicia Guard.","Wac.Signup.PostOrder.Rovo.organization.page.subtitle":"Selecciona una organización e inicia una versión de prueba de Rovo.","Wac.Signup.PostOrder.Rovo.organization.page.title":"Selecciona una organización","Wac.Signup.PostOrder.ServiceCollection.organization.page.subtitle":"Selecciona una organización e inicia una Service Collection.","Wac.Signup.PostOrder.Strategy.organization.page.subtitle":"Selecciona una organización e inicia Strategy.","Wac.Signup.PostOrder.TWC.organization.page.subtitle":"Selecciona una organización e inicia TWC","site-setup-header-order-confirmed-description":"Hemos enviado un correo electrónico de confirmación a","site-setup-header-order-confirmed-title":"Tu pedido se ha confirmado.","site-setup-header-post-provisioning-description":"Tendrás que configurar tu sitio antes de poder usar la suscripción.","site-setup-header-post-provisioning-title":"Comencemos","Wac.Signup.PostOrder.error.message":"Si el problema continúa, ponte en contacto con el equipo de soporte con el ID de seguimiento: {traceId}. ","Wac.Signup.PostOrder.error.title":"No sabemos qué ha salido mal","Wac.Signup.PostOrder.PageLoading":"Cargando","JoinSiteUserDropdown.joinTeam":"Buscar mi equipo","JoinSiteUserDropdown.licenses":"Licencias","JoinSiteUserDropdown.logIn":"Iniciar sesión","JoinSiteUserDropdown.logInAlternative":"Iniciar sesión","JoinSiteUserDropdown.logOut":"Cerrar sesión","JoinSiteUserDropdown.logOutTriggerText":"Mi cuenta","JoinSiteUserDropdown.profile":"Perfil","JoinSiteUserDropdown.switchAccount":"Cambiar de cuenta","globalNav.V2.navlink.lessMinus":"Menos -","globalNav.V2.navlink.morePlus":"Más +","GlobalNav.RovoSection.Title":"Aplicaciones con tecnología de IA, impulsadas por el conocimiento de tu equipo.","globalnav.v2.subnav.tabs.aria-label-tablist":"Productos por categoría de usuario","GlobalNav.collections.strategy.title":"Colección Estrategia","GlobalNav.collections.teamwork.title":"Teamwork Collection","GlobalNav.collections.strategy.tagline":"Aplicaciones potentes para optimizar la estrategia","GlobalNav.collections.teamwork.tagline":"Aplicaciones y agentes para impulsar el trabajo en equipo","globalnav.v2.pill":"Novedad","globalnav.v2.products.featured.recommendations":"Recomendado en función de tus aplicaciones de Atlassian actuales","GlobalNav.collections.featured.featuredapps":"Aplicaciones funcionales","GlobalNav.collections.featured.recommended.apps":"Recomendado en función de tus aplicaciones de Atlassian actuales","GlobalNav.collections.Title":"Colecciones de Atlassian novedad ","GlobalNav.collections.cloudplatform.heading":"Plataforma de Atlassian Cloud","GlobalNav.collections.cloudplatform.mobilelabel":"Destacadas","GlobalNav.collections.cloudplatform.tagline":"La base conectada de tu sistema de trabajo","GlobalNav.collections.featured.atlassiancollections.title":"Colecciones de Atlassian","GlobalNav.collections.products.atlassiancloudplatform.cta":"Más información","GlobalNav.collections.tagline":"Una selección de aplicaciones diseñadas para resolver tus necesidades concretas","GlobalNav.RovoSection.PoweredBy":"Con tecnología de","globalnav.treatment.pending":"(Adquisición pendiente)","globalnav.v2.products.bitbucket.description":"Código fuente y CI/CD","globalnav.v2.products.collectionservice.description":"Presta tus servicios a gran velocidad","globalnav.v2.products.collectionsoftware.description":"Lanza software de calidad rápidamente","globalnav.v2.products.collectionstrategy.description":"Optimiza la estrategia y los resultados con confianza","globalnav.v2.products.collectionteamwork.description":"Potencia el trabajo en equipo optimizado","globalnav.v2.products.compass.description":"Catálogo de software para equipos","globalnav.v2.products.confluence.description":"Todo el conocimiento en el mismo sitio","globalnav.v2.products.dx.description":"Mide la productividad y el impacto de la IA","globalnav.v2.products.focus.description":"Planificación estratégica a escala empresarial","globalnav.v2.products.guard.description":"Seguridad en la nube mejorada","globalnav.v2.products.jira.description":"Gestión flexible de proyectos","globalnav.v2.products.jiraalign.description":"Valor y planificación del trabajo en toda la empresa","globalnav.v2.products.jpd.description":"Registra y prioriza las ideas","globalnav.v2.products.jsm.description":"Presta servicio a alta velocidad","globalnav.v2.products.loom.description":"Actualizaciones de vídeo rápidas y asíncronas","globalnav.v2.products.pipelines.description":"Automatización de CI/CD escalable","globalnav.v2.products.rovo.description":"Transforma el trabajo en equipo con la inteligencia artificial","globalnav.v2.products.rovodev.description":"Agentic AI para desarrolladores","globalnav.v2.products.tabs.business-teams":"Equipos empresariales","globalnav.v2.products.tabs.developers":"Desarrolladores","globalnav.v2.products.tabs.everyone":"Destacadas","globalnav.v2.products.tabs.it-professionals":"Profesionales de TI","globalnav.v2.products.tabs.leadership-teams":"Equipos de liderazgo","globalnav.v2.products.tabs.product-managers":"Gestores de productos","globalnav.v2.products.talent.description":"Conocimiento sobre la planificación de la plantilla","globalnav.v2.products.trello.description":"Trabajo visualizado y organizado","globalnav.v2.subnav.tabs.see-all-apps":"Ver todas las aplicaciones","globalnav.v2.subnav.tabs.see-all-apps-arialabel":"Ver el enlace de todas las aplicaciones","globalnav.v2.productseveryone.title":"Productos destacados","globalnav.v2.products.featured.new":"Nuevos productos","AutoCompleteSearchBar.dropdown.announcement":"{resultsCount} resultados mostrados para el término de búsqueda \"{searchTerm}\"","globalnav.v2.search-bar.ai-enabled.placeholder":"Busca o pregunta algo como \"¿Cuánto cuesta Jira?\"","globalnav.v2.search-bar.placeholder":"Buscar palabras clave","globalnav.search.clear-button":"Borrar entrada de búsqueda","globalnav.search.submit-button":"Enviar búsqueda","globalnav.searchresult.see-all":"Ver todo","global-nav.contact-sales-cta.label":"Contacto","nav.skipToContent":"Saltar al contenido","GlobalNav.collections.solutions.atlassiancloudplatform.cta":"Más información","GlobalNav.collections.solutions.atlassiancloudplatform.tagline":"La base conectada de tu sistema de trabajo","GlobalNav.collections.solutions.atlassiancloudplatform.title":"Plataforma de Atlassian Cloud","GlobalNav.collections.solutions.mobilelabel":"Soluciones","globalnavv2.subnav.teams.links.agile-devops":"Metodología ágil y DevOps","globalnavv2.subnav.teams.links.column.by-industry":"Por sector","globalnavv2.subnav.teams.links.column.by-team-size":"Por tamaño del equipo","globalnavv2.subnav.teams.links.column.by-use-case":"Por caso práctico","globalnavv2.subnav.teams.links.column.solution":"por solución","globalnavv2.subnav.teams.links.column.teamtype":"Por tipo de equipo","globalnavv2.subnav.teams.links.enterprise":"Enterprise","globalnavv2.subnav.teams.links.government":"Gobierno","globalnavv2.subnav.teams.links.it":"TI","globalnavv2.subnav.teams.links.it-service-management":"Gestión de servicios de TI","globalnavv2.subnav.teams.links.marketing":"Marketing","globalnavv2.subnav.teams.links.non-profit":"Organizaciones sin fines de lucro","globalnavv2.subnav.teams.links.professional-services":"Servicios profesionales","globalnavv2.subnav.teams.links.retail":"Comercio minorista","globalnavv2.subnav.teams.links.service-management":"Gestión de servicios","globalnavv2.subnav.teams.links.small-business":"Pequeños negocios","globalnavv2.subnav.teams.links.software":"Software","globalnavv2.subnav.teams.links.software-development":"Desarrollo de software","globalnavv2.subnav.teams.links.startup":"Startup","globalnavv2.subnav.teams.links.strategy-and-planning":"Estrategia y planificación","globalnavv2.subnav.teams.links.team-collaboration":"Colaboración de Equipos","globalnavv2.subnav.teams.links.telecommunications":"Telecomunicaciones","globalnav.v2.search-bar.ai-enabled.tooltip":"Busca o pregunta cualquier cosa","globalnav.v2.search.label":"Buscar","globalnavv2.mobile.navlink.signin":"Iniciar sesión","globalnavv2.mobile.navlink.signin.ariaLabel":"Enlace de Iniciar sesión","productPageNav.atlassian-logo-label":"Logotipo de Atlassian","globalnavv2.subnav.resources.community.content":"Aprende, conecta y crece con la Comunidad de Atlassian","globalnavv2.subnav.resources.community.title":"Community","globalnavv2.subnav.resources.customer-support.content":"Haz preguntas, informa de errores y danos tu opinión","globalnavv2.subnav.resources.customer-support.title":"Atención al cliente","globalnavv2.subnav.resources.find-partners.content":"Consultoría, formación y soporte para la personalización de productos","globalnavv2.subnav.resources.find-partners.title":"Buscar un partner","globalnavv2.subnav.resources.links.agile":"Metodología ágil","globalnavv2.subnav.resources.links.developer-support":"Soporte para desarrolladores","globalnavv2.subnav.resources.links.enterprise-support":"Soporte Enterprise","globalnavv2.subnav.resources.links.general-inquiries":"Dudas generales","globalnavv2.subnav.resources.links.get-started":"Empieza ya","globalnavv2.subnav.resources.links.learning":"Atlassian Learning","globalnavv2.subnav.resources.links.partner-support":"Soporte por parte de partners","globalnavv2.subnav.resources.links.pricing-billing":"Precios y facturación","globalnavv2.subnav.resources.links.product-advice":"Asesoramiento sobre productos","globalnavv2.subnav.resources.links.product-documentation":"Documentación del producto","globalnavv2.subnav.resources.links.project-collaboration":"Colaboración en proyectos","globalnavv2.subnav.resources.links.project-management":"Gestión de proyectos","globalnavv2.subnav.resources.links.purchasing-billing":"Compras y licencias","globalnavv2.subnav.resources.links.resources":"Recursos","globalnavv2.subnav.resources.links.support":"Soporte","globalnavv2.subnav.resources.links.team-playbook":"Manual de estrategias del equipo","globalnavv2.subnav.resources.links.technical-support":"Servicio técnico","globalnavv2.subnav.resources.migration-program.content":"Recursos y soporte para tu transformación","globalnavv2.subnav.resources.migration-program.title":"Atlassian Ascend","globalnav.v2.resources.title":"Recursos","globalnav.v2.try-now-compass-subtitle":"Mejora tu experiencia de desarrollador","globalnav.v2.try-now-connie-subtitle":"Todo el conocimiento en el mismo sitio","globalnav.v2.try-now-dropdown-see-all-products":"Ver todos los productos","globalnav.v2.try-now-exp-button-label":"Obtener gratis","globalnav.v2.try-now-jira-subtitle":"Gestión flexible de proyectos","globalnav.v2.try-now-jpd-subtitle":"Registra y prioriza las ideas","globalnav.v2.try-now-jsm-subtitle":"Prestación de servicios de alta velocidad","globalnavv2.menu-back":"Atrás","globalnavv2.menu-icon.close":"Cerrar menú","globalnavv2.menu-icon.open":"Abrir menú","globalnavv2.menu-icon.toggle":"Mostrar/ocultar menú","productPageNav.logo-label":"Logotipo de Atlassian","globalnavv2.subnav.whyatlassian.customers.content":"Casos prácticos e historias centrados en el trabajo en equipo","globalnavv2.subnav.whyatlassian.customers.title":"Clientes","globalnavv2.subnav.whyatlassian.fedramp.content":"Soluciones que cumplen los requisitos del sector público","globalnavv2.subnav.whyatlassian.integrations.content":"Conecta miles de aplicaciones a tus productos de Atlassian","globalnavv2.subnav.whyatlassian.integrations.title":"Marketplace","globalnavv2.subnav.whyatlassian.platform.content":"Nuestra plataforma segura, fiable y profundamente integrada","globalnavv2.subnav.whyatlassian.platform.title":"Plataforma","globalnavv2.subnav.whyatlassian.resilience.content":"Infraestructura de alto rendimiento y de nivel empresarial","globalnavv2.subnav.whyatlassian.resilience.title":"Resistencia","globalnavv2.subnav.whyatlassian.systemofwork.content":"El modelo de Atlassian sobre la colaboración de los equipos","globalnavv2.subnav.whyatlassian.systemofwork.title":"Sistema de trabajo","globalnavv2.subnav.whyatlassian.trustcenter.content":"Garantiza la seguridad, la conformidad y la disponibilidad de tus datos","globalnavv2.subnav.whyatlassian.trustcenter.title":"Trust Center","globalnav.v2.whyatlassian.title":"¿Por qué Atlassian?","globalNavigation.Navlink.solutions":"Soluciones","globalnavv2.logo-label":"Logotipo de Atlassian","globalnavv2.navlink.businessteams":"Equipos empresariales","globalnavv2.navlink.developers":"Desarrolladores","globalnavv2.navlink.enterprise":"Enterprise","globalnavv2.navlink.featured":"Destacadas","globalnavv2.navlink.itprofessionals":"Profesionales de TI","globalnavv2.navlink.leadershipteams":"Equipos de liderazgo","globalnavv2.navlink.productmanagers":"Gestores de productos","globalnavv2.navlink.products":"Productos","globalnavv2.navlink.resources":"Recursos","globalnavv2.navlink.whyAtlassian":"¿Por qué Atlassian?","compoundSubNav.defaultCta.contactSales":"Contactar con ventas","globalNavigation.Navlink.enterprise":"Enterprise","globalNavigation.Navlink.products":"Productos","globalNavigation.Navlink.resources":"Recursos","globalNavigation.Navlink.whyAtlassian":"¿Por qué Atlassian?","wacGlobalNavigation.logo-label":"Logotipo de Atlassian","genearl-signin-prompt.email-label":"Correo electrónico","genearl-signin-prompt.header.subtext":"Inicia sesión en tu cuenta para disfrutar de una experiencia más personalizada.","genearl-signin-prompt.header.title":"Tienes la sesión cerrada.","genearl-signin-prompt.login-button":"Iniciar sesión","gwp.accountSignin.formError":"Se está tardando más de lo esperado en empezar. Comprueba tu bandeja de entrada para ver si el pedido se ha realizado correctamente o ponte en contacto con nosotros .","gwp.accountSignin.userSignupError":"Se está tardando más de lo esperado en empezar. Actualiza la página e inténtalo de nuevo o ponte en contacto con nosotros .","gwp.accountSignin.emailPlaceholder":"tunombre@empresa.com","gwp.accountSignin.helperText":"Usar el correo electrónico del trabajo ayuda a encontrar compañeros de equipo y a impulsar la colaboración.","gwp.accountSignin.invalidEmail":"Introduce una dirección de correo electrónico válida.","gwp.accountSignin.invalidEmailIcon":"El correo electrónico no es válido","gwp.accountSignin.validEmailIcon":"El correo electrónico es válido","gwp.accountSignin.workEmail":"Correo electrónico del trabajo","gwp.signinForm.loginText":" Inicia sesión ","social.label.signin":"inicia sesión con {provider}","gwp.accountSignin.submit":"Iniciar sesión","BxpUiSignup.SignupForm.or":"O seguir con","return-to-product-modal.header.text":"Continúa por donde lo dejaste.","return-to-product-modal.header.welcome":"Hola de nuevo, {name}","return-to-product-modal-v2.header.go-to":"Ir","return-to-product-modal.header.go-to":"Ir","WacSignupForm.signupOfferingIncludesFeaturesFreeBitbucket":"Incluye minutos de compilación e integración nativa con jira de Git LFS fácilmente ampliable, segura y fiable","WacSignupForm.signupOfferingIncludesFeaturesFreeBundleJSD":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesFreeConfluence":"Empieza a colaborar en equipo{newline}Aumenta la transparencia{newline}Recopila todos los conocimientos{newline}Compila contenido admirable","WacSignupForm.signupOfferingIncludesFeaturesFreeJSD":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesFreeJSDFI":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesFreeJSWFI":"Escala prácticas ágiles{newline}Consolida los flujos de trabajo{newline}Amplía la visibilidad{newline}Planificación, supervisión y publicación","WacSignupForm.signupOfferingIncludesFeaturesFreeJiraProductDiscovery":"Registra las ideas y los datos desde cualquier parte{newline}Prioriza el trabajo que tendrá más impacto{newline}Mantén informadas a las partes interesadas para que puedan participar{newline}Integrado completamente con Jira Software para facilitar las entregas","WacSignupForm.signupOfferingIncludesFeaturesPremiumConfluence":"Accede a todas las funciones{newline}Empieza a colaborar en equipo{newline}Registra todos los conocimientos{newline}Compila contenido admirable","WacSignupForm.signupOfferingIncludesFeaturesPremiumJSD":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesPremiumJSDFI":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesPremiumJSWFI":"Accede a todas las funciones{newline}Escala prácticas ágiles{newline}Consolida los flujos de trabajo{newline}Planifica, supervisa y publica","WacSignupForm.signupOfferingIncludesFeaturesSocialProofText":"Más de 65 000 equipos de todo el mundo ya confían en esta solución","WacSignupForm.signupOfferingIncludesFeaturesSocialProofTextBitbucket":"Gestión del código fuente y CI/CD","WacSignupForm.signupOfferingIncludesFeaturesSocialProofTextConfluence":"Más de 75 000 equipos de todo el mundo ya confían en esta solución","WacSignupForm.signupOfferingIncludesFeaturesSocialProofTextJSD":"Impulsa equipos de servicios de alta velocidad","WacSignupForm.signupOfferingIncludesFeaturesSocialProofTextJiraProductDiscovery":"Transforma las ideas de productos en impacto empresarial","WacSignupForm.signupOfferingIncludesFeaturesSocialProofTextTownsquare":"Simplifica tus informes de estado","WacSignupForm.signupOfferingIncludesFeaturesStandardConfluence":"Accede a todas las funciones{newline}Empieza a colaborar en equipo{newline}Registra todos los conocimientos{newline}Compila contenido admirable","WacSignupForm.signupOfferingIncludesFeaturesStandardJSD":"Conecta a los equipos empresariales, de desarrollo y de operaciones de TI en una sola plataforma{newline}Ofrece una experiencia de asistencia rápida y de gran calidad en todos los equipos{newline}Responde a los cambios y mantén los servicios en funcionamiento{newline}Colabora en una plataforma{newline}Resuelve los incidentes con rapidez","WacSignupForm.signupOfferingIncludesFeaturesStandardJSDFI":"Accede a todas las funciones{newline}Resuelve incidencias en equipo{newline}Responde rápidamente a preguntas comunes{newline}Automatiza la gestión de incidentes","WacSignupForm.signupOfferingIncludesFeaturesStandardJSWFI":"{newline}Accede a todas las funciones{newline}Escala prácticas ágiles{newline}Consolida los flujos de trabajo{newline}Planificación, supervisión y publicación","PasswordStrength.passwordModerate":"Seguridad de contraseña: moderada","PasswordStrength.passwordStrong":"Seguridad de la contraseña: fuerte","PasswordStrength.passwordVeryStrong":"Seguridad de la contraseña: muy fuerte","PasswordStrength.passwordWeak":"Seguridad de contraseña: débil","WacSignupForm.FirstImpressions.noCreditCardRequiredFooter":"No se necesita tarjeta de crédito","WacSignupForm.SimpleSignup.devopsHeader":"Tu conjunto de aplicaciones ya está listo.","WacSignupForm.accountIdMisMatch":" Se ha producido un error. Actualiza la página e inténtalo de nuevo. ","WacSignupForm.alwaysFreeForUpto":"Siempre gratuito para hasta 10 usuarios.","WacSignupForm.beaconExplore":"Descubre los productos de Atlassian","WacSignupForm.beaconRequireProducts":"Beacon requiere al menos un producto de Atlassian. No hay productos asociados a esta cuenta: cambia de cuenta o examina el paquete de Atlassian.","WacSignupForm.bitbucketAccountDuplicate":"Marca esta casilla si prefieres una cuenta nueva con el mismo nombre que la del sitio de abajo.","WacSignupForm.bitbucketCreateNewOrgInfoMessage":"Tenemos que crear una nueva organización de Atlassian, ya que actualmente no tienes ninguna organización en la gestión centralizada de usuarios de Atlassian. Si tienes alguna duda, ponte en contacto con nuestro equipo de soporte para obtener ayuda .","WacSignupForm.bitbucketMissingOrgsInfoMessage":"Si una organización no aparece en el menú desplegable, ponte en contacto con nuestro equipo de soporte para obtener ayuda .","WacSignupForm.bitbucketOrgCreationEstimatedTimeMessage":"Este proceso no tardará más de un par de minutos.","WacSignupForm.bitbucketOrgCreationPreparingProductMessage":"Estamos preparando tu producto.","WacSignupForm.bitbucketOrganizationIdFieldLabelMessage":"Crearemos tu espacio de trabajo en esta organización","WacSignupForm.bitbucketSubmitButtonTextMessage":"Aceptar y crear el espacio de trabajo","WacSignupForm.bitbucketWorkspaceIdFieldErrorMessageCMT":"El ID del espacio de trabajo no es válido. Los ID del espacio de trabajo solo pueden contener letras minúsculas, números, guiones y guiones bajos.","WacSignupForm.bitbucketWorkspaceIdFieldHelperMessage":"El ID del espacio de trabajo solo puede contener letras minúsculas, números, guiones y guiones bajos.","WacSignupForm.bitbucketWorkspaceIdFieldLabelMessage":"Tu nuevo espacio de trabajo","WacSignupForm.bitbucketWorkspaceIdTakenErrorMessageCMT":"Este ID del espacio de trabajo ya está en uso. Prueba con otro ID.","WacSignupForm.ccpSiteMigrationFollowStepsBelow":"a continuación.","WacSignupForm.ccpSiteMigrationRequiresSupport":"La migración a este sitio requiere un poco de ayuda adicional por nuestra parte.","WacSignupForm.ccpSiteMigrationStepAdditionalDetailsFieldName":"Detalles adicionales","WacSignupForm.ccpSiteMigrationStepAdditionalInfo":"3. En el campo {AdditionalDetailsFieldName}, introduce el número de autorización o la URL de Cloud a los quieres aplicar tu versión de prueba de migración a Cloud.","WacSignupForm.ccpSiteMigrationStepChoose":", elige","WacSignupForm.ccpSiteMigrationStepDCLicense":"de la licencia de Data Center y haz clic en","WacSignupForm.ccpSiteMigrationStepExtendProductTrials":"Ampliar las versiones de prueba de los productos","WacSignupForm.ccpSiteMigrationStepHelp":"Necesito más ayuda","WacSignupForm.ccpSiteMigrationStepProductTrials":"Versiones de prueba de productos","WacSignupForm.ccpSiteMigrationStepSEN":"SEN","WacSignupForm.ccpSiteMigrationStepSelect":"1. Selecciona","WacSignupForm.ccpSiteMigrationStepSelectThe":"2. Selecciona el","WacSignupForm.ccpSiteMigrationfollowSteps":"Por favor, sigue estos pasos una vez que","WacSignupForm.ccpStartNewSiteRequiresSupport":"La creación de un sitio nuevo requiere un poco de ayuda adicional por nuestra parte.","WacSignupForm.claimedMigrationSource":" Tu versión de prueba extendida ya está activada. Parece que alguien ya ha activado esta versión de prueba. Inicia sesión en my.atlassian.com o ponte en contacto con el administrador del sitio para obtener más información. ","WacSignupForm.cloudEulaText":" Al hacer clic a continuación, aceptas las Condiciones de servicio de Atlassian Cloud y la Política de privacidad . ","WacSignupForm.cloudFree":"Cloud Free","WacSignupForm.cloudPremium":"Cloud Premium","WacSignupForm.cloudStandard | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#creating-tests-using-the-tunnel | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/integrations/slack.html | Slack | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations Slack Slack Send automatic notifications to a Slack channel of your choice when tests fail. Connecting to Slack Using Reflect ’s Slack integration, you can be notified about the status of your Reflect tests directly within your Slack workspace. To get started, connect our Slack app by navigating to the Settings section within Reflect and selecting the Integrations tab. You can find the Slack integration under the Messaging section: After clicking Connect , you’ll be shown the permissions that the Reflect Slack app is requesting, and will be prompted to approve or deny access: Note The Reflect Slack app requests the ability to view your Slack workspace’s channel list, and also requests access to post messages to a channel within your Slack workspace. The Reflect app does not have access to view any messages within your Slack workspace. After connecting to your Slack workspace, you will be prompted to choose the default channel where notification messages will be sent to: Setting up Notifications Once your Slack workspace is connected to Reflect , you can now set up Slack notifications within the Suites workflow. Using the Suites workflow builder, you can specify exactly when Slack notifications should be sent, as well as specify which channel should receive the notification. For example, if you test in multiple environments (e.g. a QA environment and a Staging environment), you can set up separate Suite workflows that send failure notifications to different Slack channels depending on the environment that’s being tested. Each Slack notification will contain the name of the Suite along with its current pass/fail status, total run time, pass rate, and the total number of tests that ran: For more information on setting up a Suite workflow that contains Slack notifications, visit our Suites workflow documentation . In this section : Slack Connecting to Slack Setting up Notifications Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/manage-tests/suites.html | Suites | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Suites Suites Orchestrate regression test plans by combining test cases, configurations, and notifications. A suite encompasses a complete regression testing plan, from the individual test cases and their environments to the email notifications on failures. Suites can be executed manually in the web application, via periodic schedule, or via the Suites API. Suite execution results are stored and accessible for the duration of your account’s retention window. Creating a Suite From the main Suites List, create a new suite by clicking the “Create Test Suite” button and providing a name for the suite in the modal. From there, move on to building and configuring the suite as described in the following sections. To delete a suite, use the dots menu on the suite detail page, and accept the confirmation dialog. Building a Suite A suite is primarily a composition of workflow actions and the execution of a suite follows a sequential path through the workflow, completing actions one at a time. Reflect supports the following types of actions: Run Tests. Execute an ordered collection of tests sequentially or in parallel, and optionally apply configuration overrides to the test executions. Decision. Choose which of two workflow actions to execute next based on the pass/fail outcome of the previous action. Call API. Execute an HTTP request to an external system. Send Email. Send individual test failure emails, or a summary digest email describing the state of the suite execution. Send Slack. Send a Slack notification to a channel of your choosing that reports the state of the suite execution. Wait. Wait for some amount of time before continuing in the workflow. When you create a new suite, Reflect adds the default workflow, which consists of a Run Tests action, followed by a Decision action. The Decision action has a Send Email action attached to its failure path. Thus, this workflow will execute 0 or more tests, and if any one of them fails, send a digest email to the users in your account. You can edit any action in the suite workflow on the suite detail page by clicking on the action to open the configuration panel on the right side. To add new actions, click the (+) symbol anywhere in the workflow to open the actions panel on the left. Run Web Tests To change the tests or their order in a Run Web Tests action: Click the Run Web Tests block in the workflow Click the “Change” button to open the tests modal Click “Add Tests” at the bottom of the modal to select tests to run and close the modal Reflect supports Cross-Browser testing for tests using the Desktop device profile. Cross-browser testing is configured in the Run Tests action, and Reflect supports the latest version of all modern browsers, including Chrome, Safari, Firefox and Edge. To configure a Run Tests action to use cross-browser testing, toggle on or off the browser selections above the tests list in the action configuration. Note Only desktop tests are supported for running in non-Chrome browsers - if you select any non-desktop tests Chrome is the only option. Use the “Details” panel dropdown to toggle the parallelism setting for the tests’ execution. AUTOMATIC RETRIES Reflect supports the ability to automatically retry a Run Tests action a preconfigured number of times. This is useful in cases where the tests cannot be made to run reliably and/or deterministically. To enable automatic retries, toggle ON the “Retry on Failure” setting and choose a retry limit. Note If parallelism is turned on and multiple browsers are configured, then parallelism is enabled within a single execution of the tests list against a browser. If parallelism is not enabled the full list of tests will be executed for each browser independently and sequentially. For example, Reflect will execute the list of tests for Chrome, then Firefox, then Edge if those three browsers are selected and parallelism is not enabled. Finally, click “Save” on the workflow to commit the updates. Run Mobile Tests The Run Mobile Tests step lets you include mobile test executions in your Suite workflow. You can use it to test mobile app functionality at specific points in the workflow - for example, after web tests or before a decision step. When you add a Run Mobile Tests step, the right-side panel lets you: Set a custom name for the action (e.g., “Smoke Tests”). Choose a platform (iOS or Android). Select a specific app build, or enable the toggle to run tests with the latest app build automatically. View and manage available app builds, including version, status, and creation date. Run API Tests The Run API Tests step lets you include API calls in your Suite. You can use it to run one or more API tests at a specific point in the workflow - for example, after a mobile test or before a decision step. This step is useful when you want to trigger an API based on the outcome of a previous action, or when you want to reuse existing API tests across multiple Suites. When you add a Run API Tests step, the right panel lets you: Set a custom name for the action (e.g., "Run smoke tests"). Enable parallelism to run tests at the same time. Set retry behavior (None, 1–3 times). Select the API tests to run from your test library. This approach helps you reuse existing API tests throughout your Suite, instead of rebuilding them step by step. Data-driven Tests Any test within a Run Tests action can be configured to run as a data-driven test . A data-driven test executes multiple “instances” of a particular test with different parameter values for each instance. For example, a data-driven test allows you to verify that a given workflow within your application works as expected for the different role-based access controls (RBAC) defined in your application. Consider the configuration below: This setup instructs Reflect to execute the “Create a Record” test that defines two parameters: username and password . This Suite is set up to run this test four times for four different usernames, each sharing the same password. To create a data-driven variant, you must first define at least one parameter for your test so that you can override values sent to the test. Once a test has a parameter, a plus button will appear on this screen which allows you to create data-driven variants. The default value for each parameter will be pre-populated, but can be edited to contain whatever value you’d like, including containing a function or variable reference. Each test instance will run and will appear in its own row in the “Tests” table in the suite execution detail page. Note Reflect also supports running data-driven tests by uploading data from your own data store, such as a database or spreadsheet. Check out our API docs for instructions. Importing and Exporting Suites You can import or export test data in CSV format directly from the test parameters spreadsheet when running web, API, or mobile tests in a test suite. This functionality lets you manage test data outside of the UI while still running your suites through Reflect, either by uploading a CSV in the UI or using the API. You can find these options at the bottom of the test parameters sheet, within each Run Web Test, Run API Test, and Run Mobile Test action. Import CSV : Checks that all required parameters are present and in the correct format before loading the data into the suite. Export CSV : Available when a suite already contains test data. Generates a CSV file in the correct format for the Import CSV option, ensuring compatibility in both the UI and the run data-driven suites API. Sharing state across tests In more advanced testing scenarios, it may be necessary to take data that’s created in an earlier test, and use it in one or more later tests. For example, at the beginning of your Suite you may want to execute a test that creates a new user, and then log in as that newly created user in one or more subsequent tests. To accomplish this, you can configure tests within a Suite such that a Parameter (i.e. input) of a test references a Variable (i.e. output) of a prior test. Within a Run Tests workflow action, click on Change Tests and then select the parameter of a test that needs to reference state from a prior test. Choose to insert a variable, and you’ll be presented with an option to reference a variable from a prior test: Within the modal, choose your desired variable by first selecting the Run Tests workflow action that contains the test you want to reference, then select the desired test, and finally select the desired variable associated with that test: In order to reference a prior variable, its associated test must be guaranteed to execute before the test that’s referencing it. You can always reference variables in tests that are in a prior Run Tests workflow action. If the current workflow action has parallelism turned off, then you can also reference prior tests within the current Run Tests workflow action. Send Email The Send Email action can be configured to send either a summary digest email with the current status of the suite execution, or individual emails for each test failure (thus far) in the suite execution. The digest email includes information about the test pass rate, run time, and the failed test steps for any failed test runs. Send Slack The Send Slack action sends a notification to the channel of your choosing which reports the current state of the suite execution. In order to use this workflow action, you must first connect your Slack workspace from within the Settings section of Reflect . Wait The Wait action can be configured to delay execution for some amount of time before moving on to the next step in the workflow. Configuring a Suite The Run Tests action executes tests individually, and as such, you can alter the environment or behavior of the browser for these test runs. The Define Environment Settings workflow action is at the start of every Suite workflow, and allows you to change the hostname and variables within the test definition to be executed, as well as set browser properties like Local Storage and cookie values. Any execution overrides configured on the suite are re-evaluated for each Run Tests action. That is, if you have a dynamic variable in the overrides and multiple Run Tests actions in the suite’s workflow, the dynamic variable will be generated twice. Executing in different environments It’s common to record tests against one environment, such as a dedicated QA or staging environment, and then run those tests against other environments (such as production). Using a hostname override , you can execute a suite against different environments without creating multiple tests or otherwise changing the workflow. To execute a Run Tests action against a different environment: Click the “Run Test Suite” button when viewing the suite detail page Find the “Hostnames” section, and enter the original hostname that the test was recorded with, and then enter the replacement hostname that the test run should load instead. You can replace multiple hostnames. Click the “Run Suite” button in the modal to execute the suite with the override. (optional) Save these overrides on the suite (as described above) to automatically apply them whenever the suite is executed. In the example above, we are replacing qa.example.com with staging.example.com:1234, which means that the replacement hostname is specifying a different port for the destination hostname of 1234. Note The URL path, protocol, and query parameters will remain the same when overriding a hostname. If a port was specified in the original URL, it will be preserved unless a new value is specified in the hostname override. Additional overrides HTTP query parameters can be applied to the test’s URL and this enables specialized behavior such as bypassing authentication flows with a short-lived token, as in Firebase’s auth tokens . This parameter will be appended to the start URL of each test when test execution begins. If the parameter already is present in the start URL, the parameter’s existing value will be overwritten. Cookies, request headers and browser storage are other types of overrides that can be saved on a suite or supplied at run-time. Scheduling a Suite In addition to the on-demand methods of invocation, you can schedule a suite to execute automatically within Reflect . To create a schedule, click the “Change” button beneath the suite name: Next, select your desired schedule from the options in the modal and click the “Save” button: Reflect will now automatically trigger a suite execution at the scheduled times. Executing a Suite To execute a suite, click the “Run Test Suite” button. This opens the Run Suite modal, which displays the default execution overrides configured for the suite. You can change these overrides in-line for this specific execution, as described in Configuring a Suite . When you click “Run Suite” to confirm the configuration, the suite execution is queued in Reflect and you are redirected to the suite execution detail page. Integrating with CI/CD Suites can be executed automatically via our CI/CD integrations , or by using Reflect ’s Suite API . Since every suite has a name, each suite also has a transformed identifier based on the name. The identifier, or “slug”, is a lower-case string that removes some special characters from the name and replaces spaces with a hyphen (-). The suite identifier is shown at the top of the suite detail page next to the suite’s name: Use this identifier (e.g., regression-test-plan) as the suite-id when integrating with the Suites API or our CI/CD integrations. Viewing Suite Results The execution detail page has four different sections, all of which dynamically update as the suite execution progresses. Statistics Reflect provides high-level metrics for individual suite results, along with cumulative stats for a given suite as well as across all suites. The following metrics are shown for individual suite results : Total Tests. The number of test instances in this execution. Test Pass Rate. The pass rate for all test runs within suite executions in the last 30 days. This value reflects a moving 30-day window, meaning it always shows performance over the most recent 30 days. It cannot be reset or configured to start from a specific date. Wall Clock Time. The time between initiating the suite execution and its completion or cancellation. Cumulative Execution Time. The sum of individual execution time for all test runs in this execution. The following metrics are shown when viewing the suite configuration page, and represent cumulative stats for a given suite : Total Executions. The number of executions of this suite in the past 30 days. Test Pass Rate. The pass rate for all test runs within this suite in the past 30 days. Avg. Suite Run Time. The average wall clock time from start to completion for all executions of this suite in the past 30 days. Cumulative Execution Time. The sum of individual execution time for all test runs within this suite in the past 30 days. Finally, the following metrics are shown when viewing the Suites list page, and represent cumulative stats across all suites : Total Executions. The number of executions across all suites in the last 30 days. Test Pass Rate. The pass rate for all test runs within suite executions in the last 30 days. Avg. Suite Run Time. The average wall clock time from start to completion for all executions in the last 30 days. Cumulative Execution Time. The sum of individual execution time for all test runs within suite executions in the last 30 days. Workflow The Workflow section displays the current state of the workflow for this suite execution. If the suite execution is still running, you will see the workflow status update in real-time. You can click on any action in the workflow to open the detail panel on the right side in read-only mode. (Once the execution is initiated, it cannot be modified.) Failures The Failures section displays any test runs which have failed in the execution, as well as the test step(s) in the runs which failed. You can open the individual test run by clicking “View Test Run”. Tests Finally, the “Tests” table at the bottom displays the individual test instances in the suite, grouped by their browser and execution overrides. Within this section you can toggle between a Data Driven view, which shows results in a condensed tabular format, or a Run Details view, which shows test results in a flattened list. Re-run Failed Tests When a suite execution completes and there were failed tests, you can re-run those failed tests within the suite execution. This is useful because it allows you to edit the tests or make fixes to them, while still preserving the suite execution’s overrides or parameterized inputs. The re-run of the suite execution is treated as a new “attempt”, and is displayed on the same suite execution detail page as the original. To re-run a suite with failed tests, view the suite execution detail page and click “Re-run Failed Tests”. The new suite execution will only execute the failed tests, and the new test results will overwrite or update the suite execution’s overall results. One exception is that if newly-passing tests cause a new Decision branch to be taken, that will execute tests or actions that didn’t run originally. Once the new suite execution attempt has completed, the combined results will be shown on the execution detail page by default. But you can view previous execution attempts using the dropdown at the top right corner. Canceling a Suite A suite execution which is still in-progress can be canceled by clicking the “Cancel Execution” button at the top right. Canceling an execution prevents any additional tests from being executed, regardless of the workflow action that is currently being executed. Note Tests that are already executing will still run to completion and their results will be saved and available in Reflect . In this section : Suites Creating a Suite Building a Suite Run Web Tests Run Mobile Tests Run API Tests Data-driven Tests Sharing state across tests Send Email Send Slack Wait Configuring a Suite Executing in different environments Additional overrides Scheduling a Suite Executing a Suite Integrating with CI/CD Viewing Suite Results Statistics Workflow Failures Tests Re-run Failed Tests Canceling a Suite Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.notion.com/en-gb/integrations/asana | Asana Integrations | Connect your apps with Notion Notion Features Notion AI Build, write, automate Agents Handles manual tasks Enterprise Search Find answers instantly Meeting notes Perfectly written by AI Docs Simple & powerful Knowledge base Centralise your knowledge Projects Manage any project Sites Publish anything, fast Get started Explore AI use cases See what Notion AI can do Browse marketplace Templates for everything View integrations Connect your apps with Notion Download web clipper Save from the web into Notion Try the Notion desktop app for a faster experience Download app Mail Calendar AI Enterprise Pricing Explore Teams Eng & Product Design Marketing IT Team size Startups SMBs Enterprise Education Learn Help Centre Notion Academy Customer stories Blog Community Partner programmes Build API Templates Security Consultants Request a demo Log in Get Notion free ← Integrations Asana Add to Notion Overview Asana powers businesses by organizing their work in one space. Use the link preview to see Asana tasks directly in a Notion page, or use a synced database to bring your Asana projects into Notion databases – and use database filters, views, rollups, and relations to create custom views of your projects, so that everyone across your team can see the project status. How to use To create a preview of Asana content in Notion , paste any Asana link into Notion, then select Paste as preview . You can also type /asana in any Notion page and a menu will appear, allowing you to paste links directly If it’s your first time using Asana with Notion, you will be prompted to authorize the integration. Follow the prompts to complete the authorization process. Once authorized, you will see a detailed preview of the linked content To sync data from Asana into a Notion database , copy an Asana link to a project or task, paste the link into Notion and select Paste as database . A Notion database with Asana properties will appear and tasks will start populating automatically Please note this is not a 2-way sync. Your data will be duplicated into Notion at the moment of import, and won’t sync any changes. Learn more about Notion's synced databases To import your data from Asana into Notion , follow this guide Made by Notion Category Productivity Collaboration Features Link preview Synced database Developer links Website Terms / privacy Email support Report an issue All third-party trademarks (including logos and icons) referenced herein are the property of their respective owners. Unless specifically designated as Made by Notion, integrations are not supported or maintained by Notion. The third-party products or services that integrations connect to are Non-Notion Applications (as defined in Notion’s Master subscription agreement or Personal Terms of Use , as applicable). By enabling any integration or otherwise using the Notion integration gallery, you agree to Notion’s Integration Gallery Terms . More integrations PortalWith Create Client Portal with Notion STR Desk Sync Vacation Rental data with Notion in seconds VECTOR AI Your AI Partner Emon Sync Outlook Emails to Notion Notixel Automate your data flow between Notion and Microsoft Excel. neuforms the most affordable typeform alternative to build forms English (UK) Cookie settings © 2026 Notion Labs, Inc. Company About us Careers Security Status Terms & privacy Your privacy rights Download iOS and Android Mac and Windows Calendar Web clipper Resources Help centre Pricing Blog Community Integrations Templates Partner programmes Notion for Enterprise Small business Personal Explore more → | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/recording/private-environments.html#content-wrapper | Private Environments | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Private Environments Private Environments Reflect Supports multiple ways to test non-public web applications. Reflect Tunnel Our recommended method for testing local and private environments is to use the Reflect Tunnel , a desktop application that can be installed on your local machine or in your company’s infrastructure. The Reflect Tunnel registers with the Reflect API and establishes a secure, encrypted connection to the cloud test infrastructure. When the Reflect Tunnel is enabled, all web requests initiated in a Reflect test are proxied through the Tunnel, allowing your Reflect tests to access local or private environments accessible to the machine on which the Reflect Tunnel is running. Installation The Reflect Tunnel is a native, cross-platform application that can be run on Windows, macOS, or Linux. This feature is available to all Reflect accounts, regardless of usage tier. The Reflect Tunnel can be downloaded by using our Downloads page . Windows and macOS On Windows and macOS devices, the Reflect Tunnel runs as a system tray application. After installing and running the Reflect Tunnel application, the application will reside in the system tray by using the icon shown below: macOS Windows Troubleshooting the missing Reflect Tunnel icon in the system tray If the Reflect Tunnel icon does not appear on your Windows machine's system tray, this issue may be caused by the system firewall settings. To resolve this, ensure that Reflect Tunnel is permitted through the firewall on all network types: Domain, Private, and Public. Perform the following steps to verify that Reflect Tunnel is allowed through the firewall: Open the Control Panel and click System and Security . Click Windows Defender Firewall . In the Windows Defender Firewall left navigation pane, click Allow an app or feature through Windows Defender Firewall . Select the "the reflect_tunnel.exe" checkbox from the Allowed apps and feature list , and ensure that the Domain , Private , and Public checkboxes are selected. Note If Reflect Tunnel is not listed under the apps and feature list, click Allow another app to manually add it. After updating the firewall settings, restart your system and relaunch Reflect Tunnel to ensure the icon appears in the system tray. LINUX The Linux version of the Reflect Tunnel is a binary executable that can be run by using the command-line or configured to run as a daemon process (For example, by using systemd): ./reflect_tunnel -settings <location-of-settings-file> Starting the Tunnel For the Reflect Tunnel to act as a proxy for your Reflect tests, you must associate the Tunnel with your Reflect account. This is done by entering your Reflect API key into the Reflect Tunnel settings. Your Reflect API key can be found on the Account Information page in the Settings section Reflect . This is the same API key used when invoking the Reflect API directly or using one of our CI/CD integrations . If you have not already generated an API Key for your Reflect account, you can use the button on this page. Windows and MacOS To link your Reflect Tunnel to your account, click the icon in the system tray/menu bar and select the ‘Settings’ option: This menu option will open a web browser to the Settings view for your Reflect Tunnel: The Settings view has the following configuration options: Device Name : This is the name that will be associated with your Tunnel, and it is the name that will appear when you choose a Tunnel when creating or running tests Reflect . By default, this will be set to the device name of your computer. API Key : This is the linkage between your Tunnel and your Reflect Account. This must match the API Key associated with your Reflect Account. To connect the Tunnel, click the ‘Enable Reflect Tunnel’ toggle. If the Tunnel connects successfully, you’ll see that the toggle is enabled a lot. Aine will appear, stating that the Tunnel is connected. The tray icon will be updated to indicate that the tunnel is connected. LINUX To start the Tunnel, you’ll first need to create a JSON file that looks like the following: { "deviceName": "Your Tunnel Name", "apiKey": "your-api-key" } Pass the location of the settings file to the reflect_tunnel application as a command-line argument: ./reflect_tunnel -settings <location-of-settings-file> When running the command-line application, the tunnel will attempt to connect using the API Key provided in the settings JSON file. If the connection is established successfully, you will see a log line indicating that the connection is successful. Creating Tests using the Tunnel When creating a test in Reflect , the option to route all traffic by using a Tunnel is presented by using a dropdown to the right of the ‘Starting URL’ field: This option is also available when running automated tests directly from Zephyr : Running Tests using the Tunnel Running individual tests When running a test, you also have the option to choose whether to route all traffic from that test run to a Tunnel. When running an individual test, you can choose to route traffic through a Tunnel by clicking the dropdown in the bottom-left of the Run Test modal and selecting your desired Tunnel: Running a suite of tests To run all tests in a test suite by using a Tunnel, first select the Suite and click the ‘Define Environment Settings’ box in the Workflow settings of the Suite. In the sidebar, choose the Tunnel that you’d like all future executions of this Suite to use: If you invoke a test suite directly using the UI, you’ll also see this same Tunnel option in the Run Suite modal. Running tests using Zephyr Finally, when running tests by using Zephyr a Tunnel, you can choose to run your tests by using a Tunnel by selecting the dropdown next to the ‘Starting URL’ field in the Test Script tab of an individual test case, or the dropdown next to the ‘Browser’ field when running tests from the Test Cycle player: Configuring access The list of all Tunnels connected to your Reflect Account is viewable by navigating to the Settings section and clicking the ‘Local / Private Environments’ section from the sidebar: From this view, administrators can also disable the Reflect Tunnel feature for your Reflect account by turning off the toggle next to the ‘ Reflect Tunnel’ heading and clicking ‘Save Changes’. Using a Static IP An alternative approach to testing private environments is enabling your account's Static IP feature. Some QA or staging environments may be restricted to only allow visitors from a specific IP address or set of IPs. By default, Reflect it assigns IP addresses to its cloud browsers from a range of dynamic IPs, which means they cannot access an IP-restricted environment. To support testing these environments, Reflect you can provide a static IP address for your account. This forces all cloud browsers (i.e., recordings and test runs) to egress from Reflect the same IP address. You can then add this IP address to the list of “allowed” IP addresses in your environment’s network ACL. Note Provisioning a static IP for your account is charged as an add-on to your subscription. For more information or to see a demo, please contact us at [email protected] . In this section : Private Environments Reflect Tunnel Installation Starting the Tunnel Creating Tests using the Tunnel Running Tests using the Tunnel Configuring access Using a Static IP Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.atlassian.com/ru/enterprise/contact?formType=product-features | Contact Atlassian for Enterprise Solutions | Atlassian Перейти к содержанию Enterprise Обзор Успешно Ресурсы Больше + Связаться с отделом продаж Enterprise Enterprise Связаться с отделом продаж Назад Связаться с отделом продаж Обзор Успешно Ресурсы Войти Связаться с отделом продаж Обзор Успешно Ресурсы Войти Интересующая тема: возможности продукта цены и расчет стоимости варианты миграции платежи и лицензирование техническая поддержка Задайте нам вопросы о функциях и возможностях интересующего вас продукта или услуги. Электронная почта вашей компании * При указании личных доменов электронной почты возникнет ошибка. Имя * Фамилия * Компания * Должность * Каким продуктом или услугой вы интересуетесь? * Cloud Data Center Продукты Cloud Atlassian Guard Bitbucket Compass Confluence Jira Jira Product Discovery Jira Service Management Jira Service Management Assets Jira Service Management Virtual Service Agent Loom Rovo Service Collection Strategy Collection Teamwork Collection Trello Услуги Консультационные услуги При отправке вопросов, касающихся нескольких продуктов, выберите продукт с наибольшим количеством пользователей. Ваш вопрос * Укажите такие данные, как номера SEN (SEN-123456), EN (E-XXX) и наличие пробного периода. Администраторы продукта, посмотрите, как найти номер SEN или EN . Отправляя эту форму, я подтверждаю свое согласие с Политикой конфиденциальности Atlassian. Да, я хочу получать по электронной почте рекламные сообщения, в том числе новости о продуктах, мероприятиях и прочем, от Atlassian и дочерних компаний. Отправить Возникла ошибка. Повторите попытку позже. Дорожные карты возможностей Узнайте, что мы планируем для продуктов Cloud и Data Center. Посмотреть дорожные карты Продукты Cloud Premium Узнайте о расширенных возможностях продуктов корпоративного уровня. Ознакомиться с расширенными возможностями Дополнительные ресурсы для предприятий Просмотрите ресурсы, отфильтрованные по возможностям продуктов Cloud и Data Center. Просмотреть ресурсы Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Обратная связь Продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы корпоративного уровня Смотреть все ресурсы Copyright © 2026 Atlassian Политика конфиденциальности Уведомление о сборе персональных данных Условия использования Импрессум русский ▾ | 2026-01-13T09:29:43 |
https://www.linkedin.com/products/hubbedin-ai-resume-builder/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click#main-content | AI Resume Builder | LinkedIn Skip to main content LinkedIn HubbedIn in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in AI Resume Builder AI-Powered Coaching Software by HubbedIn See who's skilled in this Add as skill Try now Report this product About HubbedIn's Resume Builder is an AI-powered tool designed to simplify the resume creation process. It assists job seekers in crafting professional resumes effortlessly, offering personalized suggestions and rephrasing sentences to meet specific job requirements. Our AI tool aims to elevate job seekers' applications by ensuring your resumes stand out and accurately reflect your achievements and skills. Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software CoachHub - The digital coaching platform CoachHub - The digital coaching platform AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Yoodli AI Roleplays Yoodli AI Roleplays AI-Powered Coaching Software Sign in to see more Show more Show less HubbedIn products AI Video Interviewer AI Video Interviewer Video Interview Software Find a Hiring Manager Find a Hiring Manager AI-Powered Coaching Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:43 |
https://support.smartbear.com/reflect/docs/en/integrations/github.html | GitHub | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations GitHub GitHub Connect to GitHub to allow Reflect to run tests on every Pull Request and mark PRs as passing/failing. Connecting to GitHub You need to connect your GitHub account to Reflect in order to receive status updates with the results of your test runs on your GitHub pull requests. To connect to GitHub, go to Settings > Integrations , find the GitHub integration, and click the ‘Connect’ button: You’ll be prompted to sign-in to GitHub if you are not already signed in, and then you’ll be prompted to authorize Reflect to read and write the commit status for your repositories. Click “Authorize” and then you will be redirected back to the Configuration page. You should see your authorized GitHub username displayed when clicking ‘View Settings’ under the GitHub integration: Note The user who authorizes the GitHub integration must have commit access to your GitHub repository. After the GitHub integration is added, you can now set up Test Suite executions to automatically add a “Check” to any GitHub Pull Request. When invoking the Reflect API to kick off a Test Suite execution, you’ll need to pass along the repository name, the GitHub organization name, and the SHA associated with the Pull Request. This lets Reflect know which Pull Request should be associated with this Test Suite execution. Please refer to our API docs for information on how to pass these values in the API request body. When configured correctly, you should see that the Pull Request is immediately updated with a check to indicate that the Reflect tests are running: After the Test Suite execution is complete, the Pull Request check will be updated with a link to the results, and will be set with its final pass/fail status: In this section : GitHub Connecting to GitHub Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:43 |
https://www.digitalcameraworld.com/buying-guides/the-best-150-600mm-lenses#section-tamron-150-600mm-g2 | The best 150-600mm lenses | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Don't miss these Lenses If I were starting my Pro Sports Photography career again, I’d buy this 180-600mm lens - it's currently got $200 off and under $2,000 Compact Cameras The best full-frame compact cameras – portable powerhouses DSLR Cameras The best DSLR in 2025: Chunky, classic camera designs still loved today Lenses The best lenses for the Canon EOS R50: this camera is a proper little powerhouse and deserves the right lenses Bridge Cameras The best bridge camera: ultra-zoom cameras for far-off subjects Lenses 12 lenses of Christmas: Laowa and Viltrox try to outdo each other for most new lenses in the same month! Lenses The best Nikon Z lenses: the top buys for your Nikon Z-series mirrorless Cameras The best Panasonic Lumix cameras: from Micro Four Thirds to full-frame and bridge cameras Lenses Hands-on Canon RF 45mm f/1.2 STM review: The super-fast glass that's super affordable – and punches way above its price point Lenses The best lenses for the Sony ZV-E10 & ZV-E10 II: smart choices for vlogging and just about any other genre of video and stills photography Lenses The best lenses for the Canon EOS M50 and M50 Mark II: these mini marvels will make the most of your slimline camera Lenses The best Nikon lenses for DSLRs in 2026: brilliant lenses for Nikon F-mount cameras Lenses The best lenses for the Sony A6400: let me help you pick some perfect lenses for your pocket powerhouse Sony body Cameras Best camera for macro photography in 2025: This gear gets great close-up shots! Lenses The best lenses for the Fujifilm X-T5: make the most of all those megapixels Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets Cameras Lenses The best 150-600mm lenses: super-telephoto zooms to get close to the action Buying guides By Matthew Richards Contributions from Lauren Scott last updated 22 December 2025 These are the best 150-600mm lenses to really cover the distance for action, sports and wildlife photography When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . (Image credit: Lauren Scott) Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Share Share by: Copy link Facebook X Whatsapp Pinterest Flipboard Share this article Join the conversation Follow us Add us as a preferred source on Google I don’t like to think I’m lazy and I honestly don’t mind ‘zooming with my feet’, but that’s not always possible. To get as close as I’d ideally like, I’d have to jump the barriers at sporting events, sprout my own pair of wings at airshows, and risk getting eaten alive by hungry wildlife. Sometimes discretion is the better part of valor, and a 150-600mm lens can get you close to the action from a respectable (and safe) distance. Originally pioneered by Sigma and adopted by Tamron , 150-600mm lenses used to be a rare breed. Camera manufacturers often didn’t make their own and even if they did, some of the old DSLR examples have now been discontinued. To make this guide as useful as possible, I've included not only ‘150-600mm’ lenses that are currently available, but also a selection of super-telephoto zooms that cover a fairly similar range. The debate on the 'best' zoom range, of course, rages on – many photographers prefer the best 70-200mm lenses or the best 100-400mm lenses as their favorite working distance. However, the 150-600mm outstrips them both in terms of sheer range and raw distance. Matthew Richards Social Links Navigation Lens tester Matthew Richards is a photographer and journalist who has spent years using and reviewing all manner of photo gear. He is Digital Camera World's principal lens reviewer, and as such he has tested more primes and zooms – including plenty of 150-600mm optics – than most people have had hot dinners! The quick list Best mirrorless 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports View at Amazon View at Adorama View at Adorama View at Best Buy Best for mirrorless For Sony E and L-mount mirrorless cameras, this lens is a worthy successor to a DSLR classic. It's got a weather-sealed build and produces pin-sharp imagery. Read more below Best DSLR 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 View at Amazon Best for DSLRs Still going strong for Nikon F and Canon EF mounts, Tamron's G2 lens is a refresh of a classic that boasts excellent autofocus and stabilisation. Read more below Best MFT 3. Olympus M.Zuiko 75-300mm f/4.8-6.7 II View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Best Micro Four Thirds Delivering a 300-1200mm equivalent zoom range thanks to the MFT crop factor, this is an incredibly powerful super-tele zoom that doubles your reach. Read more below Best Nikon Z 4. Nikon Z 180-600mm f/5.6-6.3 VR View at BHPhoto View at Adorama View at Amazon View at Best Buy Best Nikon Z Running very close to the 150-600mm focal range, this lens shaves a bit off the wide end, but still delivers real shooting versatility in a lightweight package. Read more below Best Canon RF 5. Canon RF 100-500mm f/4.5-7.1L IS USM View at Amazon View at Adorama View at Crutchfield View at Target Best Canon RF You lose a little at the tele end but gain a little at the wide end, and Canon's RF 100-500mm delivers brilliant images throughout the whole range. Read more below Best Sony 6. Sony FE 200-600mm F5.6-6.3 G OSS View at Adorama View at Best Buy View at Amazon View at Target Best Sony While Sony users can use Sigma's true 150-600mm, this capable telezoom is a solid Sony-made alternative. The optical stabilisation is highly effective. Read more below Load the next products ↴ Multi-mount mirrorless 7. Tamron 150-500mm f/5-6.7 Di III VC VXD View at KEH Camera View at Adorama View at Amazon View at Best Buy Multi-mount mirrorless Originally just for Sony FE mount, this zoom lens from Tamron has since been made available for Fujifilm X and Nikon Z. It's not quite 600mm, but it's still a great lens. Read more below 10x zoom 8. Sigma 60-600mm f/5-6.3 DG OS HSM | S View at Amazon View at Amazon 10x zoom Need a little more play at the wide end? This Sigma-made lens offers a whopping 10x zoom range for DSLR shooters, and optically it impresses. Read more below Best Fuji 9. Fujifilm XF150-600mm F5.6-8 R LM OIS WR View at Adorama View at Amazon View at Best Buy View at Target Best Fujifilm X Delivering a whopping equivalent zoom range of 229-914mm, this lens certainly provides telephoto reach. It can even be used with 1.4x and 2.0x teleconverters! Read more below Best 150-600mm lenses Why you can trust Digital Camera World Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out how we test. 150-600mm lenses Here are my picks of the best 150-600mm lenses you can buy right now, for both mirrorless and DSLR cameras. Sigma 150-600mm Sports (Image credit: Digital Camera World) 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports The Sports lens finally comes to E-mount and L-mount mirrorless cameras! Our expert review: Specifications Mount: Sony E, Leica L Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Stepper motor Stabilizer: 4-stops Minimum focus distance: 0.58-2.8m Maximum magnification: 0.34x Filter thread: 95mm Dimensions: 109.4 x 265.6mm Weight: 2,100g Today's Best Deals View at Amazon View at Adorama View at Adorama View at Best Buy Reasons to buy + Superb sharpness + One of few mirrorless options Reasons to avoid - Chunky and heavy - Non-removable tripod collar A retooling of an already excellent DSLR lens, the Sigma 150-600mm f/5-6.3 DG DN OS Sports is the complete package for Sony and Leica L shooters. Pairing superb internal optics with an all-around excellent, weather-sealed build, this heavy-duty zoom lens is a big customer, but is really the only game in town for 150-600mm as far as users of the aforementioned mounts are concerned. Of course, that wouldn't matter if the lens itself was no good. Fortunately, it's excellent. The optical path is a little different from the DSLR version, including 25 elements arranged in 15 groups, and it produces impressive sharpness throughout the entirety of the zoom range. There's some inevitable fall-off in the corners, but not enough to worry about, and it's the sort of thing that will be hidden anyway when you're shooting with a shallow depth of field. The autofocus is excellent, though you'll need to make sure your camera is set up in the optimal way to take advantage of it. The build quality of the lens is also impressive – while no one is going to pretend this is a lightweight lens, it handles well, with tactile zoom and focus rings and a series of on-body controls for functions like AF speed, stabilization intensity, and in a new addition for the mirrorless version, Zoom Torque control to adjust the resistance of the zoom ring. This is an all-around excellent lens that's absolutely worth the money for E-mount and L-mount users. See our full Sigma 150-600mm f/5-6.3 DG DN OS Sports review Image 1 of 4 (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ The lens inherits the high-end features and handling of the older version for DSLRs, in a smaller, lighter package. Design ★★★★★ The design is very refined, while build quality is excellent and includes extensive weather-seals. Performance ★★★★★ Excellent inherent sharpness is further boosted in real terms by highly effective optical stabilization. Value ★★★★★ It’s a pro-grade super-telephoto zoom with a ‘consumer’ price tag, making it standout value. Tamron 150-600mm G2 (Image credit: Future) 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 Tamron’s ‘Generation 2’ edition of its 150-600mm lens is seriously revamped Our expert review: Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Mount: Canon EF, Nikon FX, Sony A Elements/groups: 21/13 Diaphragm blades: 9 Autofocus: Ultrasonic (ring-type) Stabilizer: 4.5-stops Minimum focus distance: 2.2m Maximum magnification: 0.16x Filter thread: 95mm Dimensions: 108 x 260mm Weight: 2,010g Today's Best Deals View at Amazon Reasons to buy + Improved autofocus and stabilisation + Good sharpness in long section Reasons to avoid - No optical stabilization in Sony-fit - Sharpness lacking at shorter zoom This G2 (Generation 2) edition of Tamron’s 150-600mm lens is upgraded in pretty much every facet of its features, handling and performance. The LD (Low Dispersion) element count goes from one to three, and BBAR (Broad-Band Anti-Reflection) coatings add to the older lens’s eBAND (Extended Bandwidth and Angular-Dependency) coatings, to further suppress internal reflections. The uprated autofocus system delivers faster performance, better able to track moving subjects and the redesigned VC (Vibration Compensation) system gives class-leading 4.5-stop effectiveness, plus two additional switchable modes. The second mode is for panning and the third applies stabilisation only during exposures, making it easier to track erratically moving objects. However, the optical stabilizer is only featured in the Canon and Nikon mount editions of the lens. With the Sony A-fit edition, you’ll need to rely on in-camera stabilization (note that for Sony mirrorless cameras using the Sony E-mount, you should check out the Tamron 150-500mm f/5-6.7 Di III VC VXD ). Going one better than the Sigma 150-600mm lenses, a new flex zoom lock enables you to lock the zoom at any position, rather than just at settings for which a focal length is marked on the barrel. It also matches the Sigma lenses with compatibility for an optional USB dock, which Tamron calls a ‘TAP-in Console’, for applying customization and firmware upgrades. There’s only a marginal Increase in size and weight over the original Tamron (see below), but the G2 gets superior weather-seals and a fluorine coating on the front element. Overall build quality feels superior. Living up to Tamron’s claims, the G2’s autofocus speed and the effectiveness of its image stabilization are excellent. Image quality is very good overall, but sharpness is a bit of a mixed bag. In our tests, it proved slightly less sharp than the original Tamron lens at short to medium zoom settings, but rather sharper in the 400-600mm sector. It’s a good trade-off, as you’ll usually find yourself using the lens towards the long end of its zoom range. See our full Tamron SP 150-600mm f/5-6.3 Di VC USD G2 review Swipe to scroll horizontally Features ★★★★☆ The ‘Generation 2’ edition of this lens has a strong feature set with upgraded autofocus and stabilization systems. Design ★★★★☆ The design is pretty crafty and I like that this lens is the best part of a kilogram lighter than Sigma’s competing Sports lens for DSLRs. Performance ★★★★☆ Image quality and overall performance are impressive overall but the lens could be sharper at the short end of its zoom range. Value ★★★★☆ The Tamron is keenly priced for a DSLR-focused 150-600mm with high-end specs and handling. OM System 150-600mm (Image credit: James Artaius) 3. OM System M.Zuiko 150-600mm f/5.0-6.3 IS A 150-600mm lens by name, but goes way beyond that in reality Our expert review: Specifications Mount: Micro Four Thirds Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Yes Stabilizer: Yes (6 stops at 150mm, 5 at 600mm / 7 stops at 150mm, 6 at 600mm with Sync-IS) Minimum focus distance: 0.56-2.8m Maximum magnification: 0.35x (0.7x full frame equivalent) Filter thread: 95mm Dimensions: 264.4x109.4mm (fully extended) Weight: 2,065g Today's Best Deals View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Reasons to buy + Phenomenal 600-1200mm range + Up to 7 stops of stabilization + IPX1 weather proofing Reasons to avoid - Sharpness is disappointing - A very big and heavy lens - Very expensive The Micro Four Thirds system has a 2x crop factor, relative to a full-frame camera. This means that, although this lens has an advertised 150-600mm focal range, when fitted to an MFT body its field of view will be equivalent to a 300-1200mm full-frame lens. Consequently, this lens offers immense reach for capturing distant subjects, while up to 7 stops of image stabilization helps keep things steady when you're zoomed in to the max. Keen lens nerds may have spotted that this lens looks very similar to the Sigma 150-600mm f/5-6.3 DG DN OS Sports (number 1 on this list). And that's because it is essentially the same lens, adapted for use on Micro Four Thirds bodies. While that has its benefits, as a full-frame lens it does mean the OM System M.Zuiko 150-600mm feels very bulky and heavy compared to more typical MFT optics. During our time reviewing the OM System M.Zuiko 150-600mm , we came away a little disappointed by the lens's overall sharpness, which was significantly down on the performance of the Sigma 150-600mm. But if you must have telescope-rivalling levels of zoom for your Micro Four Thirds camera, this is the only lens to go for. Read our full OM System M.Zuiko 150-600mm f/5.0-6.3 IS review Image 1 of 3 (Image credit: Paul Burrows) (Image credit: Paul Burrows) (Image credit: Paul Burrows) Swipe to scroll horizontally Features ★★★★☆ Top of the features list is the humungous 1200mm maximum ‘effective’ focal length, backed up by as much as 7-stop stabilization. Design ★★★★☆ Build quality is tough, with IPX1 weather-proofing, although it’s big and heavy for a Micro Four Thirds lens. Performance ★★★☆☆ Levels of sharpness are a bit disappointing, especially at longer zoom settings. Value ★★★☆☆ It’s not particularly good value, especially in comparison to the likes of Sigma and Tamron 150-600mm full-frame zooms. 150-600mm alternatives There are a few lenses that give a similar, but slightly different, focal length range to a 150-600mm – and below are some of those which are worth considering: Nikon Z 180-600mm (Image credit: Matthew Richards) 4. Nikon Z 180-600mm f/5.6-6.3 VR A relatively affordable telephoto option for Z-mount mirrorless. Our expert review: Specifications Mount: Nikon Z Elements/groups: 25/17 Diaphragm blades: 9 Autofocus: Linear stepping motor Stabilizer: Yes Min focus distance: 1.3-2.4m Max magnification: 0.25x Filter thread: 95mm Dimensions (WxL): 110x315.5mm Weight: 1955g Today's Best Deals View at BHPhoto View at Adorama View at Amazon View at Best Buy Reasons to buy + Effective 5.5-stop VR + Razor-sharp throughout range + Customisable function buttons Reasons to avoid - Somewhat bulky/heavy - No VR on/off switch This big zoom is as close as Nikon has got to matching the 150-600mm focal length – and it's an outstanding lens. Earning the full five stars in our review, the Nikon Z 180-600mm f/5.6-6.3 VR offers tack-sharp image quality right the way through that zoom range. While it's a relatively hefty lens, it's light enough that you'll be able to use it handheld for a decent chunk of time. We particularly love the four customisable function buttons, which sit just under where the thumb naturally falls. A particular asset of this lens is its optical VR (Vibration Reduction) system, which is rated to provide up to 5.5 stops of effective compensation. This makes the far end of the telephoto much more useable hand-held, and helps you make the most of all that gorgeous sharpness. Great for sports, wildlife and other types of telephoto shooting, the Nikon Z 180-600mm f/5.6-6.3 VR is the best choice for approximating the 150-600mm focal range on Nikon Z cameras. Read our full Nikon Z 180-600mm f/5.6-6.3 VR review Image 1 of 4 (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) Swipe to scroll horizontally Features ★★★★★ Compared with Nikon’s F-mount 200-500mm zoom, this one has longer telephoto reach and more effective 5.5-stop optical stabilization. Design ★★★★★ The lens is impeccably built with extensive weather-seals and is noticeably lighter than Nikon’s 200-500mm lens. Performance ★★★★★ Sharpness and clarity are exceptional, even at the longest zoom setting, backed up by super-fast autofocus and highly effective stabilization. Value ★★★★☆ It’s pricier than the F-mount 200-500mm lens but well worth the extra outlay. Canon RF 100-500mm (Image credit: Future) 5. Canon RF 100-500mm f/4.5-7.1L IS USM Not a 150-600mm - but a great option for Canon full-frame mirrorless Our expert review: Specifications Mount: Canon RF Elements/groups: 20/14 Diaphragm blades: 9 Autofocus: Dual Nano USM Stabilizer: Yes Min focus distance: 0.9-1.2m Max magnification: 0.33x Filter thread: 77mm Dimensions (WxL): 93.8x207.6mm Weight: 1530g Today's Best Deals View at Amazon View at Adorama View at Best Buy View at Target Reasons to buy + Lacks the reach of a true 150-600mm + Brilliant image quality Reasons to avoid - Disappointing AF speed on older EOS R bodies - Narrow maximum aperture The Canon RF 100-500mm f/4.5-7.1L IS USM is the first super-telephoto zoom lens for EOS R-system mirrorless cameras. This is a high-quality lens with its L-series build, and even has a heat shield coating for coping with shooting in challenging weather conditions, whether it’s hot or cold. Plus its 5-stop image stabilization will help you deliver sharp shots when shooting handheld with slower shutter speeds and in low light. It lacks the reach of a 150-600mm at its telephoto lens - but compensates for this with its widest tele setting. See our full Canon RF 100-500mm review Image 1 of 2 (Image credit: Matthew Richards/Digital Camera World) (Image credit: Matthew Richards/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ There’s a smorgasbord of features packed into this lens with optical stabilization, dual Nano USM autofocus motors and a very high-end optical path. Design ★★★★★ Flourishes include a zoom ring torque adjustment, carried forward from the EF lens, and robust weather-sealed build quality. Performance ★★★★★ Autofocus performance needs one of the more recent than original EOS R bodies to get the most out of the lens, but image quality is fabulous. Value ★★★★☆ It’s pretty good value for what it is, but this lens will nevertheless make a sizeable dent in your bank balance. Sony 200-600mm (Image credit: Sony) <a href="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" data-url="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" target="_blank" referrerpolicy="no-referrer | 2026-01-13T09:29:44 |
https://www.linkedin.com/products/hubbedin-ai-video-interviewer/ | AI Video Interviewer | LinkedIn Skip to main content LinkedIn HubbedIn in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in AI Video Interviewer Video Interview Software by HubbedIn See who's skilled in this Add as skill Try now Report this product About Our AI Interview platform empowers job seekers by providing a cutting-edge tool for enhancing interview skills. We offer realistic interview simulations tailored to specific job roles, complete with personalized feedback to refine your responses and boost your confidence. Our goal is to help you become more articulate and job-ready, ensuring you stand out in your next job interview. Similar products FaceCode FaceCode Video Interview Software HireVue HireVue Video Interview Software AI Interviewer by Hyring AI Interviewer by Hyring Video Interview Software BrightHire BrightHire Video Interview Software InCruiter InCruiter Video Interview Software BarRaiser BarRaiser Video Interview Software Sign in to see more Show more Show less HubbedIn products AI Resume Builder AI Resume Builder AI-Powered Coaching Software Find a Hiring Manager Find a Hiring Manager AI-Powered Coaching Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:44 |
https://www.linkedin.com/products/categories/video-interview-software | Best Video Interview Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Recruiter (41) Human Resources Manager (37) Recruitment Specialist (26) Human Resources Specialist (22) Talent Acquisition Specialist (21) See all products Find top products in Video Interview Software category Software used to conduct live or pre-recorded video interviews with job candidates. - Record, analyze, and share videos for employee recruitment - Use AI tools to analyze performance metrics such as facial movements, tone, and vocabulary - Centralize all candidate interviews and share across hiring personnel - Integrate recruiting workflows such as interview scheduling, email notification, and candidate ranking 165 results FaceCode Video Interview Software by HackerEarth FaceCode is the most intelligent way to conduct coding interviews. It lets you easily invite and conduct coding interviews on a collaborative, real-time code editor that automates your interview summaries. FaceCode combines objective, standardized evaluation parameters with ai-based insights for the most accurate and effortless coding interview reports ever. All to help you make the right decisions in the least amount of time. View product HireVue Video Interview Software by Hirevue From video interviews to pre-hire assessments, HireVue provides talent acquisition managers and recruiters with transformative hiring solutions. View product AI Interviewer by Hyring Video Interview Software by Hyring® Your AI Recruiter View product BrightHire Video Interview Software by BrightHire BrightHire transforms hiring quality and efficiency with AI that builds exceptional hiring plans, saves time with automated interview notes, enhances decision quality, levels up interview consistency, and gives you actionable talent insights. View product InCruiter Video Interview Software by InCruiter At InCruiter, we are revolutionizing the hiring process by offering Full Suite of Interview Intelligence Platform tailored for fast-paced recruitment needs. Founded in 2018, InCruiter’s mission is to simplify and accelerate hiring for businesses across the globe. With over 10 million minutes of interviews, 6 products, a network of 3000+ expert interviewers, and a growing base of 500+ clients, we bring top-tier automated screening tools to help organizations meet their hiring goals. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights BarRaiser Video Interview Software by BarRaiser BarRaiser's Intelligent Interview Platform is a suite of state-of-the-art tools tailored for today's fast-paced hiring needs. Our Co-pilot tool streamlines interviews with AI guidance, while the Structured Planning tool helps you focus on the right skills to be focused in an interview. The Interview Intelligence provides insightful reports and interviewer performance metrics, and the Video Interview Platform leverages recording and collaboration for efficient decision-making using AI generated highlights and notes. Uniting these tools is our mission: making interviews smarter, faster, and fairer. Experience the innovation with BarRaiser. View product FloCareer Video Interview Software by FloCareer At FloCareer, we help organizations grow their technology teams quickly, cost-effectively, and at scale. We conduct unbiased technology-based interviews led by over 6100+ interviewers. We help companies scale their tech teams by following a rigorous hiring process driven by structured interviews integrated into a video Interview as a Service platform delivered by freelance technical interviewers. We offer end to end hiring solution 1) Sourcing: Automate sourcing, attract candidates with hyper targeted marketing and conveniently engage through a pre-scheduled meeting 2) Screening Solutions: Customize your screening process effortlessly with our automated resume screening, WhatsApp-based questionnaires, & online tests. 3) Interview-as-a-Service: Optimize your hiring process with FloCareer Interview as a Service. Conduct high-quality video interviews with 6100+ expert interviewers 4) Interview Management Software: Simplify interview management with our comprehensive suite of tools View product Skills Platform: Screen, Interview, Hire Top Talent for Every Role Video Interview Software by Glider AI Glider AI, 2021 SIA winner for most innovative HR technology, provides hiring solutions including candidate screening, skill tests, video and live coding interviews, and more to scale hiring quality talent for the Enterprise, Staffing Firms, and MSPs. Glider is used by over 50% of the world’s top IT-50 suppliers and global enterprises looking to vet, place, hire, and retain quality talent at scale with confidence whether full-time or contingent, technical or non-technical roles. Global brands like Intuit, PwC, Amazon, Capital One, and FINRA trust Glider to validate candidate quality and fit across any role in any industry. On average, customers see a 3x placement rate, a 50% reduction in time-to-fill, and a 98% improvement in candidate satisfaction. For more information, visit Glider AI. View product AI Interviewer Video Interview Software by CodeSignal AI Interviewer is an AI-powered interview solution designed to help companies hire the best talent faster. With customizable assessments that adapt to each company’s specific context and unique hiring needs, AI Interviewer ensures companies can identify top candidates quickly, accelerating the hiring process while saving leaders time and maintaining a consistent interview experience. Leverage AI role-plays to see candidates’ job-relevant skills in action. AI Interviewer allows users to assess skills in communication, relationship-building, pitching, problem-solving, product knowledge, and more. Screen all of your applicants for sales, customer success, support, and other business roles. View product Talview Interviews Video Interview Software by Talview Streamline remote interviews effortlessly with Talview Interviews. Whether it's a 1:1, panel, or group interview, our platform automates scheduling, invitations, tracking, and feedback for both live and asynchronous video or audio sessions. Interview Rooms is a fully equipped virtual meeting room designed to prevent interview fraud. You can also conduct in-session coding tasks or use the whiteboard to gauge candidate potential better. One-way interviews help screen candidates during the initial rounds of interviews. They include standardized questions that candidates can record their answers to, which can then be reviewed later. Talview interviewing platform integrates with all major ATS and scheduling tools like Outlook and Calendly for a seamless experience. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:44 |
https://www.atlassian.com/de/software/loom/use-case/support | Videonachrichten für den Kundensupport verwenden | Atlassian Close Diese Seite in deiner Sprache anzeigen? Alle Sprachen Sprache auswählen 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Kostenlos testen Funktionen Funktionen erkunden Besprechungsnotizen Bildschirmrekorder Screenshots Loom AI Bearbeiten Back Lösungen Teams Anwendungsbeispiele Unternehmensgröße Teams Vertrieb Marketing Design Support Produktmanagement Engineering Anwendungsbeispiele Loom + Jira Loom + Confluence Unternehmensgröße Enterprise Back Resourcen Preise Mehr + Weniger - Kostenlos testen Back Kostenlos testen Loom für Support Mit Videonachrichten den Kundenservice optimieren Loom hilft Teams, Kundeninteraktionen maßstabsgerecht zu personalisieren, um Kunden langfristig zu binden. Hol dir Loom kostenlos Mit Videos die Kundenbeziehungen verbessern Statt sich lange E-Mails durchlesen zu müssen, können Kunden einfach Videos ansehen. Erstelle hochwertige Kundenservice-Inhalte, um Käufer zu informieren und die Kundenbindung zu verbessern. Videos sind zeitgemäß Bearbeite die Anliegen deiner Kunden mit einer persönlichen Note. So kannst du die Feedbackschleife schneller schließen. Videos sind personalisiert Erstelle individuelle Videos, um Kunden auf anschauliche Weise zu helfen, dein Produkt bestmöglich zu nutzen. Videos sind interaktiv Ermittle anhand der Video-Interaktionen, wann Kunden zusätzlichen Support benötigen. Funktionen für den Kundensupport Mühelos aufnehmen Nimm deinen Bildschirm von einem Browser, Desktop-Computer oder Smartphone aus auf, um die Bedürfnisse deiner Kunden zu erfüllen. Immer und überall teilen Sende Looms per E-Mail, Chat, Internet oder Social Media, die ohne Download angesehen werden können. Integration Ihrer Tools Loom ist mit Kundenservice-Tools wie Zendesk kompatibel und vereinfacht so den Support. Überprüfung der Ansichten Schau dir an, wann und wie Kunden mit deinen Kundensupport-Videos interagieren. Marken-Support Füge für ein einheitliches Branding dein Firmenlogo und deine Farbpalette hinzu. Kontinuierlicher Support Überprüfe Kommentare und biete zusätzliche Support-Services direkt von deinem Video aus an. Benutzern helfen und Kundenzufriedenheit verbessern Unterstütze Benutzer durch hochwertige Kundenservice-Videos. Stärkere Kundenbindung durch eine persönliche Note Kunden, die individuelle Erfahrungen mit deiner Marke gemacht haben, werden mit größerer Wahrscheinlichkeit zu Wiederholungskäufern. Loom ermöglicht eine einfache Personalisierung und kann so den Customer Lifetime Value steigern. Qualitativ hochwertiger Support durch Videos Videos sind eine lebendigere Art, mit Kunden in Kontakt zu treten, und können auch wertvoller sein. Zum Beispiel fällt es Kunden leichter, die Verwendung einer Produktfunktion zu erlernen, wenn sie sehen können, wie es funktioniert. Geringere Abwanderung durch Personalisierung Über 60 % der Kunden wandern ab, wenn eine Marke keine personalisierte Benutzererfahrung bietet. Loom bietet die erforderliche persönliche Note, um Kundenabwanderung zu reduzieren und die Metriken der Kundenzufriedenheit zu verbessern. "Loom bietet die Möglichkeit, in einem kleinen runden Fenster in der Ecke das Gesicht anzuzeigen. Das funktioniert viel besser als herkömmliche Formate, bei denen eine Audiospur über einer Animation oder einer Diashow läuft. Ein echtes Gesicht verleiht den Videos eine persönliche Note und erweckt das Storytelling zum Leben." Erica Goodell Customer Success, Pearson Loom AI dient allen, die Kunden dienen Eine klare Botschaft Loom AI entfernt automatisch Füllwörter und Pausen. Der letzte Schliff Nutze Loom AI, um Titel, Zusammenfassungen und Kapitel zu generieren, die das Engagement und die Übersichtlichkeit erhöhen. Sofortiges Teilen Loom AI entwirft im Handumdrehen E-Mails für eine ausgefeilte Präsentation. Teste Loom AI kostenlos Schnellere Aufnahmen, mehr Zeit für Kunden Endlich keine Neuaufnahmen mehr dank schneller und präziser Bearbeitung sowie einfacher Clipverwaltung. Jetzt kannst du mühelos mit asynchronen Videos einen außergewöhnlichen Kundenservice bieten. Ausprobieren Aus unserem Blog So verbesserst du mit asynchronen Videos den Kundensupport Vier Gründe, warum du für deinen Kundensupportprozess Videos benötigst Artikel lesen So nutzen wir Videos im Rahmen unserer Kundensupport-Strategie Artikel lesen Entdecke unseren Blog Entdecke Möglichkeiten, Loom zu verwenden Loom für Techniker Mehr erfahren Loom for Sales Mehr erfahren Loom für Produktmanagement Mehr erfahren Alle Anwendungsfälle ansehen Loom funktioniert überall, wo du bist. Für Mac, Windows, iOS und Android Hol dir Loom kostenlos Unternehmen Karriere Veranstaltungen Blogs Investor Relations Atlassian Foundation Presse-Kit Kontakt Produkte Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle Produkte anzeigen Resourcen Technischer Support Kauf und Lizenzierung Atlassian Community Wissensdatenbank Marketplace Mein Konto Support-Ticket erstellen Lernen Partner Training und Zertifizierung Dokumentation Ressourcen für Entwickler Enterprise Services Alle Ressourcen anzeigen Copyright © 2025 Atlassian Datenschutzrichtlinie Nutzungsbedingungen Impressum Sprache wählen Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://www.notion.com/de/product/calendar/download | Notion Calendar für Mac Notion Funktionen Notion-KI Erschaffen, schreiben, automatisieren Agenten Übernehmen manuelle Aufgaben Enterprise Suche Finde Antworten in Sekundenschnelle Smart Notes Perfekt geschrieben von der KI Dokumente Einfach und leistungsstark Wissensdatenbank Bündle dein Wissen Projekte Verwalte jede Art von Projekt Websites Veröffentliche alles Mögliche im Handumdrehen Loslegen KI-Anwendungsfälle entdecken Schau dir an, wozu die Notion-KI in der Lage ist Marktplatz durchstöbern Vorlagen für alles Mögliche Einbindungen anzeigen Verbinde deine Apps mit Notion Web Clipper herunterladen Speichere Inhalte aus dem Web in Notion Teste die Desktop-App von Notion für mehr Geschwindigkeit App herunterladen Mail Calendar KI Enterprise Tarife Erkunden Teams Entwicklung und Produkt Design Marketing IT Teamgröße Start-ups KMUs Konzerne Bildungswesen Lernen Hilfe-Center Notion Academy Erfahrungsberichte von Kund/-innen Blog Community Partnerprogramme Entwickeln API Vorlagen Sicherheit Beratung Fordere eine Demo an Anmelden Nutze Notion kostenlos Schöpfe das volle Potenzial von Notion Calendar auf dem Desktop aus Schneller auf dem Desktop. Arbeiten ohne Ablenkungen. Für Mac herunterladen → Notion Calendar gibt es für den Desktop-Browser, macOS, Windows, iOS und Android. Deutsch Cookie-Einstellungen © 2026 Notion Labs, Inc. Unternehmen Über uns Karriere Sicherheit Status Nutzungsbedingungen und Datenschutz Deine Datenschutzrechte Download iOS und Android Mac und Windows Calendar Web Clipper Ressourcen Hilfe-Center Preise Blog Community Einbindungen Vorlagen Partnerprogramme Notion für Unternehmen Kleine Unternehmen Persönlich Mehr entdecken → | 2026-01-13T09:29:44 |
https://www.linkedin.com/products/categories/ai-powered-coaching-software?trk=products_details_guest_other_products_by_org_section_product_link_result-card_subtitle-click#main-content | Best AI-Powered Coaching Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Head of Human Resources (7) Chief Executive Officer (6) Human Resources Manager (4) Salesperson (4) Human Resources Specialist (3) See all products Find top products in AI-Powered Coaching Software category Software used to improve skills using guidance enabled by artificial intelligence. - Receive daily and on-demand recommendations, tips, and support - Engage in AI-led conversation and use platform to track analytics and progress - Combine traditional coaching with continuous feedback from automated analysis - Access information and solutions with better personalization and customization over time 112 results LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software by LinkedIn LinkedIn Learning combines AI-powered coaching with realistic role play scenarios, giving job seekers and learners a safe, supportive space to practice interviews and workplace conversations. With AI-powered coaching, you can ask questions like “How do I prepare for an interview?” or “How can I change careers?” and get instant, personalized advice drawn from LinkedIn Learning’s entire expert-led course library. With role play, you can rehearse conversations by text or voice, receive real-time feedback on tone and delivery, and get tailored course recommendations to close skill gaps. Whether you’re interviewing, changing careers, or building confidence for tough conversations, LinkedIn Learning helps you practice, grow, and achieve your goals. View product LinkedIn Interview Prep AI AI-Powered Coaching Software by LinkedIn With LinkedIn Premium, you get access to Interview Prep AI, built on the power of LinkedIn’s job marketplace. Practice mock interviews with personalized questions specifically for the roles you’re applying to, so your prep matches the opportunities you care about most. Role play live with an AI interviewer that asks realistic follow-ups and get tailored feedback on your strengths and areas to improve. Only on LinkedIn can your job search and your interview prep come together in one place, helping you walk into interviews with confidence and stand out for your next opportunity. View product AI Resume Builder AI-Powered Coaching Software by HubbedIn HubbedIn's Resume Builder is an AI-powered tool designed to simplify the resume creation process. It assists job seekers in crafting professional resumes effortlessly, offering personalized suggestions and rephrasing sentences to meet specific job requirements. Our AI tool aims to elevate job seekers' applications by ensuring your resumes stand out and accurately reflect your achievements and skills. View product CoachHub - The digital coaching platform AI-Powered Coaching Software by CoachHub - The digital coaching platform CoachHub is the global leader in digital coaching. We enable organizations to deliver personalized, scalable coaching programs that drive measurable business impact across the workforce. Coaching Solutions Designed for Scale ✔️CoachHub Individual: Support long-term growth by giving employees access to world-class business coaches. ✔️CoachHub Executive™: Help senior leaders turn complexity into clarity and vision into results. ✔️CoachHub Collective: Build stronger teams through expert-led group coaching that accelerates collaboration and problem-solving. ✔️AIMY™: Our pioneering AI coach makes coaching scalable, measurable and accessible across the organization. The Business Impact ✔️Companies that partner with CoachHub see: ✔️Higher employee engagement and retention ✔️Measurable improvements in productivity and performance ✔️Stronger leadership pipelines and employer brand View product MOBILITY AI-Powered Coaching Software by Office Solution AI Labs Being able to do business “on the go” with mobile apps matters now more than ever for the customers and your workforce. As the whole world is getting hyper-connected, enterprises are moving towards mobile apps. If you want to automate your business operations and manage your entire business model easily, we at MS Office Solution can help you. We design and develop mobility solutions for your enterprise that simplify your challenging tasks and address all your business concerns. Mobile analytics captures data from the mobile apps, websites, and the web apps’ visitors to identify unique users, tracking their visits to the site, record their behavior, and prepare reports on the application performance. Capturing analytics from mobility and deriving useful insights from it is one of the major trends followed by the businesses. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Exponent Practice AI-Powered Coaching Software by Exponent Interview Prep Ace tech interviews with AI-powered feedback and peer mocks. Join thousands of tech candidates practicing interviews to land jobs. Practice real questions over video chat in a collaborative environment with personalized AI feedback and rubric evaluation. View product Yoodli AI Roleplays AI-Powered Coaching Software by Yoodli AI Roleplays Trusted by Fortune 100 companies, Yoodli helps teams ramp faster, win more deals, and communicate with confidence in their most critical conversations. As an AI-powered roleplay simulator, Yoodli supports training across sales, leadership, and customer engagement—delivering private, real-time, judgment-free coaching at scale. Teams can rehearse discovery calls, objection handling, negotiations, presentations, interviews, or feedback conversations anytime, anywhere. Yoodli provides instant feedback on clarity, confidence, and delivery, plus progress tracking to measure growth across teams. Leaders gain scalable, data-driven insights to identify strengths and coach where it matters most—ensuring practice translates into measurable results. View product Find a Hiring Manager AI-Powered Coaching Software by HubbedIn Our "Find Hiring Manager" tool is designed to significantly enhance your job search. We leverage AI to connect you directly with hiring managers, giving you the edge you need to stand out. By providing access to the email and LinkedIn profiles of hiring managers, we help you reach the right people faster. Our platform also crafts personalized messages by analyzing your resume and the job details, increasing your chances of getting hired. Plus, with our resume builder's tracker feature, you can stay informed about your resume's performance. View product UP AI Growth Companion AI-Powered Coaching Software by UP School Meet Your AI-Powered Growth Catalyst UP transforms everyday moments into breakthrough performance through personalized micro-learning that adapts to each employee's role, learning style, and growth goals. Our 30+ specialized AI coaches deliver just-in-time learning when and where your people need it most. How UP works differently: - 3-5 minute daily sessions that fit seamlessly into busy schedules - AI powered personalization that adapts to individual learning patterns and company culture - Safe practice environments for high-stakes scenarios like difficult conversations and presentations - Spaced repetition technology that ensures skills stick long-term Every day your team isn't using UP is a day of missed growth potential. Book a demo to discover. View product Artificial Intelligence for Business AI-Powered Coaching Software by Ateliware Seamlessly integrate the potential of artificial intelligence into your processes, boosting productivity and efficiency with tailored solutions. > AI Discovery: Want to implement AI but not sure where to start? We help you explore and identify the best opportunities for your business. > Proof of Concept: Know what you want but unsure if it's feasible? We create a quick PoC to test the solution's viability, discover costs, models, and the services you may need. > AI MVP: Already validated your idea and ready to launch an initial version? We develop the MVP using artificial intelligence to accelerate your go-to-market process. > Integration: Need to integrate an existing solution or add AI functionalities to your product? We handle the development. We work closely with your team to adapt the development process to your company’s specific needs, ensuring secure and customized integration. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/integrations/email-notifications.html | Email Notifications | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations Email Notifications Email Notifications Get automated alerts when tests start failing. Getting Notified When tests fail, each user within your account will be notified via email. Each email notification includes the name of the failing test and a link to the test run that reproduces the error. All test failure emails will be sent from [email protected] and will have a subject line starting with Reflect - Test Run Failed :. Note Emails will not be sent for subsequent failures of the test until the test has passed successfully at least once. Additionally, emails are not sent for failures of a single test run initiated by a user in the web UI. In this section : Email Notifications Getting Notified Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/manage-tests/folders.html#managing-folders | Folders | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Folders Folders Group related tests together in lightweight collections. Folders are a lightweight way to group a set of tests together. Managing Folders The Test List view on the Reflect main screen shows a list of all folders on the left side and a table of tests within the selected folder on the right. All accounts have at least one folder, the “All Tests” folder, which cannot be removed or renamed. You can create a new folder by clicking the “Add Folder” link at the bottom of the folders list. To rename a folder, click the pencil icon next to the folder name at the top of the Test List view. To delete a folder, click the “Delete Folder” button and accept the confirmation dialog. Changing a Test’s Folders You can modify the folders that contain a test from the Test Detail page. You can add a new folder within this view as well. In this section : Folders Managing Folders Changing a Test’s Folders Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://www.atlassian.com/de/customers/flo#content | Flo verbessert das Wohlbefinden mit den Collaboration-Tools von Atlassian Zu Inhalt springen Produkte Highlights Entwickler Produktmanager IT-Experten Business-Teams Führungsteams Alle Apps ansehen Vorgestellte Apps Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Jira Service Management High-Velocity-Service bereitstellen Atlassian-Sammlungen Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Service Collection Reaktionsschneller Service Jira Service Management Customer Service Management Assets Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Unterstützt von Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Jira Flexibles Projektmanagement Compass Softwarekatalog für Teams Pipelines Skalierbare CI/CD-Automatisierung Bitbucket Quellcode und CI/CD DX Messe die Produktivität und Wirkung der KI Rovo Dev Agentic AI für Entwickler Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Jira Product Discovery Ideen festhalten und priorisieren Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Jira Service Management High-Velocity-Service bereitstellen Guard Höhere Sicherheit in der Cloud Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Trello Organisierte und visualisierte Arbeit Loom Schnelle, asynchrone Video-Updates Jira Service Management High-Velocity-Service bereitstellen Customer Service Management Customer experiences reimagined Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Focus Strategische Planung auf Enterprise-Niveau Talent Wissensbasierte Personalplanung Align Unternehmensweite Arbeitsplanung und Wertschöpfung Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Lösungen Lösungen Nach Anwendungsfall Zusammenarbeit im Team Strategie und Planung Servicemanagement Softwareentwicklung Nach Teamtyp Software Marketing IT Nach Teamgröße Enterprise Kleinunternehmen Start-up Gemeinnützige Organisationen Nach Branche Einzelhandel Telekommunikation Professionelle Services Behörden Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Warum Atlassian? System of Work New Atlassians Plan für Team-Zusammenarbeit Marketplace Verknüpfe Tausende Apps für deine Atlassian-Produkte Kunden Fallstudien und Berichte über Teamwork FedRAMP Konforme Lösungen für den öffentlichen Sektor Stabilität Hochperformante Infrastruktur der Enterprise-Klasse Plattform Unsere tief integrierte, zuverlässige und sichere Plattform Trust Center Zuverlässige Sicherheit, Compliance und Verfügbarkeit für deine Daten Ressourcen Kundensupport Stelle Fragen, melde Bugs und gib uns Feedback Partner suchen Beratung, Schulung und Unterstützung bei der Produktanpassung Atlassian Ascend Ressourcen und Unterstützung für deine Transformation Community Schulung, Vernetzung und Weiterbildung mithilfe der Atlassian Community Support Allgemeine Anfragen Technischer Support Produktberatung Preise und Abrechnung Partnersupport Support für Entwickler Enterprise-Support Bestellung und Lizenzierung Ressourcen Projektmanagement Zusammenarbeit an Projekten Agile Team-Playbook Atlassian Learning Produktdokumentation Erste Schritte Enterprise Mehr + Kostenlos starten Zurück Produkte Highlights Entwickler Produktmanager IT-Experten Business-Teams Führungsteams Lösungen Warum Atlassian? Ressourcen Enterprise Einloggen Vorgestellte Apps Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Jira Service Management High-Velocity-Service bereitstellen Atlassian-Sammlungen Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Service Collection Reaktionsschneller Service Jira Service Management Customer Service Management Assets Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Unterstützt von Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Entwickler Jira Flexibles Projektmanagement Compass Softwarekatalog für Teams Pipelines Skalierbare CI/CD-Automatisierung Bitbucket Quellcode und CI/CD DX Messe die Produktivität und Wirkung der KI Rovo Dev Agentic AI für Entwickler Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Produktmanager Jira Product Discovery Ideen festhalten und priorisieren Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. IT-Experten Jira Service Management High-Velocity-Service bereitstellen Guard Höhere Sicherheit in der Cloud Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Business-Teams Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Trello Organisierte und visualisierte Arbeit Loom Schnelle, asynchrone Video-Updates Jira Service Management High-Velocity-Service bereitstellen Customer Service Management Customer experiences reimagined Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Führungsteams Focus Strategische Planung auf Enterprise-Niveau Talent Wissensbasierte Personalplanung Align Unternehmensweite Arbeitsplanung und Wertschöpfung Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Lösungen Nach Anwendungsfall Zusammenarbeit im Team Strategie und Planung Servicemanagement Softwareentwicklung Nach Teamtyp Software Marketing IT Nach Teamgröße Enterprise Kleinunternehmen Start-up Gemeinnützige Organisationen Nach Branche Einzelhandel Telekommunikation Professionelle Services Behörden Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Warum Atlassian? System of Work New Atlassians Plan für Team-Zusammenarbeit Marketplace Verknüpfe Tausende Apps für deine Atlassian-Produkte Kunden Fallstudien und Berichte über Teamwork FedRAMP Konforme Lösungen für den öffentlichen Sektor Stabilität Hochperformante Infrastruktur der Enterprise-Klasse Plattform Unsere tief integrierte, zuverlässige und sichere Plattform Trust Center Zuverlässige Sicherheit, Compliance und Verfügbarkeit für deine Daten Ressourcen Kundensupport Stelle Fragen, melde Bugs und gib uns Feedback Partner suchen Beratung, Schulung und Unterstützung bei der Produktanpassung Atlassian Ascend Ressourcen und Unterstützung für deine Transformation Community Schulung, Vernetzung und Weiterbildung mithilfe der Atlassian Community Support Allgemeine Anfragen Technischer Support Produktberatung Preise und Abrechnung Partnersupport Support für Entwickler Enterprise-Support Bestellung und Lizenzierung Ressourcen Projektmanagement Zusammenarbeit an Projekten Agile Team-Playbook Atlassian Learning Produktdokumentation Erste Schritte Zu Inhalt springen Produkte Highlights Entwickler Produktmanager IT-Experten Business-Teams Führungsteams Lösungen Warum Atlassian? Ressourcen Enterprise Einloggen Vorgestellte Apps Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Jira Service Management High-Velocity-Service bereitstellen Atlassian-Sammlungen Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Service Collection Reaktionsschneller Service Jira Service Management Customer Service Management Assets Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Unterstützt von Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Entwickler Jira Flexibles Projektmanagement Compass Softwarekatalog für Teams Pipelines Skalierbare CI/CD-Automatisierung Bitbucket Quellcode und CI/CD DX Messe die Produktivität und Wirkung der KI Rovo Dev Agentic AI für Entwickler Software Collection Schnelle Auslieferung hochwertiger Software Rovo Dev DX Pipelines Bitbucket Compass Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Produktmanager Jira Product Discovery Ideen festhalten und priorisieren Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. IT-Experten Jira Service Management High-Velocity-Service bereitstellen Guard Höhere Sicherheit in der Cloud Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Business-Teams Jira Flexibles Projektmanagement Confluence Das gesamte Wissen an einem Ort Trello Organisierte und visualisierte Arbeit Loom Schnelle, asynchrone Video-Updates Jira Service Management High-Velocity-Service bereitstellen Customer Service Management Customer experiences reimagined Teamwork Collection Nahtlose, produktive Teamarbeit Jira Confluence Loom Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Führungsteams Focus Strategische Planung auf Enterprise-Niveau Talent Wissensbasierte Personalplanung Align Unternehmensweite Arbeitsplanung und Wertschöpfung Strategiesammlung Zuverlässige Optimierung von Strategie und Ergebnissen Focus Talent Align Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Lösungen Nach Anwendungsfall Zusammenarbeit im Team Strategie und Planung Servicemanagement Softwareentwicklung Nach Teamtyp Software Marketing IT Nach Teamgröße Enterprise Kleinunternehmen Start-up Gemeinnützige Organisationen Nach Branche Einzelhandel Telekommunikation Professionelle Services Behörden Rovo KI-gestützte Apps – basierend auf dem Wissen deines Teams. Warum Atlassian? System of Work New Atlassians Plan für Team-Zusammenarbeit Marketplace Verknüpfe Tausende Apps für deine Atlassian-Produkte Kunden Fallstudien und Berichte über Teamwork FedRAMP Konforme Lösungen für den öffentlichen Sektor Stabilität Hochperformante Infrastruktur der Enterprise-Klasse Plattform Unsere tief integrierte, zuverlässige und sichere Plattform Trust Center Zuverlässige Sicherheit, Compliance und Verfügbarkeit für deine Daten Ressourcen Kundensupport Stelle Fragen, melde Bugs und gib uns Feedback Partner suchen Beratung, Schulung und Unterstützung bei der Produktanpassung Atlassian Ascend Ressourcen und Unterstützung für deine Transformation Community Schulung, Vernetzung und Weiterbildung mithilfe der Atlassian Community Support Allgemeine Anfragen Technischer Support Produktberatung Preise und Abrechnung Partnersupport Support für Entwickler Enterprise-Support Bestellung und Lizenzierung Ressourcen Projektmanagement Zusammenarbeit an Projekten Agile Team-Playbook Atlassian Learning Produktdokumentation Erste Schritte Flo verbessert weltweit das Wohlbefinden durch bessere Zusammenarbeit mithilfe der Atlassian Cloud-Produkte Bei uns sind alle Tools in einen nahtlosen Arbeitsbereich integriert. Das bedeutet, dass wir uns auf unsere Mission und Produktziele konzentrieren können, anstatt darüber nachdenken zu müssen, wie wir Workflows organisieren oder was wir als Nächstes tun. Hauptergebnisse 900 % mehr Deployments pro Tag 50 % kürzere Durchlaufzeit 99 % kürzere mittlere Problemlösungszeit Über Flo Branche Technologie Anzahl Benutzer Über 250 Standort Hauptsitz in London, England Weitere Informationen Durch die Zusammenführung verschiedener Abteilungen auf einer integrierten, cloudbasierten Atlassian-Plattform können die Teams von Flo nahtlos zusammenarbeiten, die Leistung nachverfolgen und ihre Workflows optimieren. Dies wirkt sich positiv auf das Unternehmen und die Kunden aus. Die internen Teams haben die Deployment-Geschwindigkeit um mehr als 900 %, die Durchlaufzeit um 88 % und die mittlere Problemlösungszeit um 99 % verbessert. Dank dieser Geschwindigkeit der Bereitstellung und des Service vermittelt die bestbewertete App von Flo über 165 Millionen Menschen weltweit ein besseres Verständnis für ihren Körper. Um eine effektive Gesundheits-App zu erstellen, mit der Menschen ihren Körper besser verstehen und darauf achten können, müssen häufig zwei völlig gegensätzliche Konzepte miteinander in Einklang gebracht werden: Wissenschaft und Emotionen, Automatisierung und die menschliche Note, Sicherheit und Offenheit. Die medizinischen Experten und Technologiespezialisten von Flo haben dieses Kunststück bravourös gemeistert, wie ihre Ergebnisse zeigen. In nur fünf Jahren hat sich Flo von einem brandneuen Periodentracker und Ovulationskalender zu einer umfassenden Gesundheits-App mit Top-Bewertungen entwickelt. Mehr als 165 Millionen Menschen nutzen die App aktuell, um ihre Gesundheit proaktiv zu überwachen und auf die Signale ihres Körpers zu hören. Sie können darin den Modus wechseln, um die für sie relevantesten Einblicke zu gewinnen (Zyklusverfolgung, Schwangerschaft oder Schwangerschaftsnachsorge) und in einer sicheren Umgebung persönliche Unterstützung von anderen zu erhalten. Das Flo-Team hat jeden Schritt dieser Entwicklung mithilfe von Atlassian erleichtert. Durch die Einführung einer umfassenden, integrierten Suite aus Cloud-Produkten von Atlassian können Mitarbeiter sich gegenseitig und auch ihre Kunden besser unterstützen. Eine neu erstellte zentrale Plattform, in der verschiedene Abteilungen zusammenarbeiten, ihre Leistung nachverfolgen und Workflows optimieren können, hat es den internen Teams von Flo ermöglicht, die Deployment-Geschwindigkeit um über 900 %, die Durchlaufzeit um 88 % und die mittlere Problemlösungszeit um 99 % zu verbessern. Wir sind von einem massiven Release pro Monat zu 10 bis 20 Produktions-Deployments pro Tag übergegangen. Außerdem haben wir den durchschnittlichen Entwicklungszyklus von 5,8 Tagen auf 2,9 Tage und die Standardabweichung von 19,8 Tagen auf 3,5 Tage reduziert." Roman Bugaev CTO Ein Katalysator für Zusammenarbeit Schon zu Beginn stand Flo vor einer Reihe komplexer Herausforderungen. Einige sind für das Arbeitsgebiet des Unternehmens typisch. Es muss beispielsweise herausfinden, wie es Technologie für maschinelles Lernen mit den Gesundheitsdaten von echten Fachleuten kombinieren, oder den Datenschutz mit dem Aufbau einer Community vereinbaren kann. Flo hatte zudem mit Problemen zu kämpfen, von denen auch andere schnell wachsende Unternehmen in jeder Branche betroffen sind. Dazu gehören die Einführung moderner Praktiken, um die Geschwindigkeit und den Erfolg zu steigern, eine schnelle Skalierung ohne Einbußen bei der Vernetzung und Qualität sowie die Remote-Zusammenarbeit über weltweit verteilte Standorte hinweg. Für jede Herausforderung nutzte das Team die Cloud-Produkte von Atlassian, um an einer Lösung zu arbeiten. Da sich Flo der Innovation und Sicherheit verpflichtet fühlt, entschied sich das Unternehmen, die Arbeit in die Cloud zu verlegen. Das ISO/IEC 27001-Zertifikat von Atlassian überzeugte Flo davon, dass die Lösung in Sachen Datenschutz und Risikomanagement eine Hilfe sein würde. "Wir haben gebührende Sorgfalt walten lassen und sichergestellt, dass die Sicherheitsfunktionen, Datenschutzpraktiken und Betriebseigenschaften von Atlassian unsere Anforderungen erfüllen. Wir haben festgestellt, dass Atlassian Cloud eine zuverlässige und ausgereifte Lösung ist, auf die auch andere Unternehmen vertrauen. Durch das Arbeiten in der Cloud können wir uns verstärkt auf unsere Plattformen konzentrieren und müssen uns bezüglich Tools oder Wartung keine Gedanken machen", erklärt CTO Roman Bugaev. "Außerdem ist die Cloud dank Features wie Audit-Protokollen sicherer und zuverlässiger, was die Einhaltung von Vorschriften angeht. Wenn wir mit Atlassian arbeiten, können wir sicher sein, dass unser System ordnungsgemäß verwaltet wird. Eine Reproduktion derselben internen Umgebung würde uns viel Zeit und Ressourcen kosten. Diese investieren wir lieber in unser eigenes Produkt." Zu Beginn führte das Engineering Bitbucket Cloud für das Codemanagement, Confluence Cloud zum Speichern von Informationen und Jira Cloud – mit Add-ons wie Jira Misc Workflow Extensions – für eine effiziente, agile Produktentwicklung ein. Dank kostenloser Social-Media-Postings und interner Champions übernahm bald das ganze Unternehmen Atlassian-Lösungen, was den Austausch von Arbeitsergebnissen und Informationen zwischen Teams und Kunden deutlich einfacher machte. Von Entwicklern und Content-Autoren bis hin zu medizinischen Experten und Kundendienstmitarbeitenden – sie alle nutzen täglich eine Vielzahl von Atlassian-Produkten. Durch das Arbeiten in der Cloud können wir uns verstärkt auf unsere Plattform konzentrieren und müssen uns bezüglich Tools oder Wartung keine Gedanken machen. Außerdem ist die Cloud dank Features wie Audit-Protokollen sicherer und zuverlässiger, was die Einhaltung von Vorschriften angeht. Roman Bugaev CTO Aufbau einer Servicekultur mit verteilten Teams Die Teams bei Flo bauen gerade eine Servicekultur auf, die das gesamte Unternehmen umfasst – technische und nicht-technische Rollen sowie vor Ort und remote arbeitende Kollegen. Dabei dienen Atlassian-Lösungen als Grundgerüst, das eine höhere Effizienz und Effektivität unterstützen soll. Nicht-technische Teams wie die der Rechts- oder Compliance-Abteilung sehen beispielsweise in Jira Service Management nach, was zu tun ist, wenn Mitarbeiter entweder neu im Unternehmen anfangen, es verlassen oder eine andere Rolle übernehmen. Communications Manager Daria Grishechkina erzählt, dass ihr Team auch eine Reihe anderer Atlassian-Produkte verwendet, um mit wichtigen Stakeholdern im Unternehmen an der Erstellung von Inhalten zu arbeiten. Sie sagt: "Sämtliche Inhalte werden mehrmals von der Rechtsabteilung, von der medizinischen Abteilung und dem Produktmanagement korrigiert und bearbeitet. So wird sichergestellt, dass wir evidenzbasierte, vertrauenswürdige Informationen bereitstellen. Wir verwenden Atlassian für jeden Schritt – von der Erstellung über die Überprüfung bis hin zur Verbreitung." Die technischen Teams von Flo nutzen ihre integrierte Atlassian-Plattform auch, um mit anderen Abteilungen zusammenzuarbeiten und sämtliche Aspekte ihrer Arbeit zu optimieren. Das Engineering nutzt Jira Service Management nicht nur für das tägliche Produktmanagement und die agile Entwicklung, sondern auch um Serviceanfragen schnell zu verwalten, Warnungen zu überwachen und Bereitschaftspläne zu koordinieren – was bei so vielen verteilten Teams in verschiedenen Zeitzonen schwierig wird. "Wir hatten eine Überwachungslösung, aber wenn in Abwesenheit eine E-Mail eingeht, kann man auf diese nur schlecht reagieren", sagt Roman. "Es war eine wirklich gute Entscheidung, die Incident-Response-Funktionen von Opsgenie in Jira Service Management zu nutzen. Jetzt verfügen alle Produktentwicklungsteams über Servicedesks und Rotationspläne, die vorschreiben, wann sie Benachrichtigungen erhalten. Dadurch können wir schneller reagieren, wenn etwas schiefläuft." Dank des vernetzten, strukturierten Servicemanagement- und Warnsystems konnte Flo die mittlere Problemlösungszeit um 99 % reduzieren und die mentale Belastung senken. Beides hat die Arbeitsmoral der Mitarbeiter verbessert. "Früher mussten alle [für die Problembearbeitung] in Slack nachsehen. Jetzt haben es die Techniker mit den organisierten Workflows und Integrationen zwischen Jira Service Management und anderen Produkten deutlich einfacher. Sie sind weniger müde und haben mehr Spaß an der Arbeit", so Roman. "Dank der Atlassian-Tools und der gut organisierten und strengen Prozesse brauchen wir nicht mehr darüber nachzudenken, wie Aufgaben erledigt werden sollen. So können wir uns darauf konzentrieren, den Benutzern einen Mehrwert zu bieten." Roman fügt hinzu, dass Integrationen zwischen Jira Service Management, Jira, Bitbucket, Confluence und anderen wichtigen Tools im Workflow (einschließlich Slack, Snyk und SonarQube) die DevOps- und ITSM-Praktiken von Flo erleichtern. Marketplace-Apps wie Dynamic Forms und Extensions for Jira Service Management bieten noch mehr Kontext und Anpassungsmöglichkeiten, die Zeiteinsparungen bringen und Mitarbeitenden helfen, fundiertere Entscheidungen zu treffen. Beispielsweise arbeiten die IT-, die Entwicklungs- und die Sicherheitsabteilung mittels Atlassian-Tools zusammen, um Probleme zu lösen, Ursachen zu identifizieren und zukünftige Probleme zu verhindern. "Wir können die Problemursache einfacher erkennen, weil wir CI/CD-Pipelines haben, in denen wir alle Deployments sehen – nicht nur diejenigen, die mit Jira-Tickets verknüpft sind, sondern auch mit Confluence, Bitbucket und Slack verknüpfte Deployments", erklärt Roman. "Bitbucket ist in Slack integriert, sodass wir sehen können, wann eine Pipeline hinzugefügt wird. Und wenn sich ein Vorfall ereignet, lässt sich ganz einfach ein Slack-Channel erstellen, über den gemeinsam daran gearbeitet werden kann. In Opsgenie werden dann alle Vorfälle auf unserem Bildschirm angezeigt. Dadurch können wir Trends erkennen; entscheiden, ob Post-Mortem-Analysen angesetzt werden sollen, und Vorfälle mit Slack-Unterhaltungen verknüpfen, um den Verlauf nachzuverfolgen." Egal, ob mehrere Techniker gemeinsam ein Problem behandeln oder medizinische Experten, Produktentwickler und Content-Autoren sich über gesundheitliche Erkenntnisse austauschen – Atlassian ist der wichtigste Servicekanal, über den Informationen zwischen Teams und Benutzern übermittelt werden. "Atlassian bringt all diese Teams zusammen", sagt Roman. "Dank der benutzerfreundlichen Bedienoberfläche und der Integrationen können unsere medizinischen Experten schnell einsteigen und mit der Arbeit beginnen." Denn je schneller sie zu arbeiten anfangen, desto schneller können sie Positives für ihr Unternehmen und ihre Kunden bewirken. Die Techniker haben es mit den organisierten Workflows und Integrationen zwischen Jira Service Management und anderen Produkten deutlich einfacher. Sie sind weniger müde und haben mehr Spaß an der Arbeit. Roman Bugaev CTO Hier steht der Mensch on vorderster Stelle Aus dem einfachen Periodentracker von Flo ist eine fortschrittliche Gesundheits- und Wellness-App geworden und die Atlassian Cloud-Produkte haben sich mit dem Unternehmen weiterentwickelt. Während das Team seine Atlassian-Lösungen weiter ausbaute und integrierte, konnte Flo die Ergebnisse seiner harten Arbeit intern und in dem bereitgestellten Service nachvollziehen. "Wir sind in einem stark umkämpften Markt tätig, daher müssen wir möglichst effizient arbeiten. Wir automatisieren und optimieren viel mit Atlassian und dadurch können wir Engpässe in unserem Prozess reduzieren und unsere Ziele schneller erreichen", erklärt Roman. "Wir sind beispielsweise von einem massiven Release pro Monat zu 10 bis 20 Produktions-Deployments pro Tag übergegangen. Außerdem haben wir den durchschnittlichen Entwicklungszyklus von 5,8 Tagen auf 2,9 Tage und die Standardabweichung von 19,8 Tagen auf 3,5 Tage reduziert." Dank dieser Effizienz kann das Flo-Team nicht nur schneller arbeiten, es hat auch mehr Zeit und Energie übrig, um sich auf das Wesentliche zu konzentrieren. Roman sagt: "Unser großes, hoch gestecktes Ziel ist es, Frauen den Zugang zu Informationen zu ermöglichen, die sie brauchen, um ihre Gesundheit und sich selbst zu priorisieren. Bei uns sind alle Tools in einen nahtlosen Arbeitsbereich integriert. Das bedeutet, dass wir uns auf diese Mission und Produktziele konzentrieren können, anstatt darüber nachdenken zu müssen, wie wir Workflows organisieren oder was wir als Nächstes tun." Flo ist bereits auf dem besten Weg, dieses Ziel zu erreichen. Und seine bisherigen Erfolge feuern das Unternehmen an, seinen Weg weiterzuverfolgen. Mit einer stärkeren Vernetzung könnte das Unternehmen Flo einen wichtigen Beitrag dazu leisten, dass Menschen auf der ganzen Welt ein besseres Verhältnis zu ihrem Körper und ihrer Gesundheit entwickeln. Wenn du mehr über die Migration zur Cloud erfahren möchtest, besuche das Cloud Migration Center . Durch die Zusammenführung verschiedener Abteilungen auf einer integrierten, cloudbasierten Atlassian-Plattform können die Teams von Flo nahtlos zusammenarbeiten, die Leistung nachverfolgen und ihre Workflows optimieren. Dies wirkt sich positiv auf das Unternehmen und die Kunden aus. Die internen Teams haben die Deployment-Geschwindigkeit um mehr als 900 %, die Durchlaufzeit um 88 % und die mittlere Problemlösungszeit um 99 % verbessert. Dank dieser Geschwindigkeit der Bereitstellung und des Service vermittelt die bestbewertete App von Flo über 165 Millionen Menschen weltweit ein besseres Verständnis für ihren Körper. Um eine effektive Gesundheits-App zu erstellen, mit der Menschen ihren Körper besser verstehen und darauf achten können, müssen häufig zwei völlig gegensätzliche Konzepte miteinander in Einklang gebracht werden: Wissenschaft und Emotionen, Automatisierung und die menschliche Note, Sicherheit und Offenheit. Die medizinischen Experten und Technologiespezialisten von Flo haben dieses Kunststück bravourös gemeistert, wie ihre Ergebnisse zeigen. In nur fünf Jahren hat sich Flo von einem brandneuen Periodentracker und Ovulationskalender zu einer umfassenden Gesundheits-App mit Top-Bewertungen entwickelt. Mehr als 165 Millionen Menschen nutzen die App aktuell, um ihre Gesundheit proaktiv zu überwachen und auf die Signale ihres Körpers zu hören. Sie können darin den Modus wechseln, um die für sie relevantesten Einblicke zu gewinnen (Zyklusverfolgung, Schwangerschaft oder Schwangerschaftsnachsorge) und in einer sicheren Umgebung persönliche Unterstützung von anderen zu erhalten. Das Flo-Team hat jeden Schritt dieser Entwicklung mithilfe von Atlassian erleichtert. Durch die Einführung einer umfassenden, integrierten Suite aus Cloud-Produkten von Atlassian können Mitarbeiter sich gegenseitig und auch ihre Kunden besser unterstützen. Eine neu erstellte zentrale Plattform, in der verschiedene Abteilungen zusammenarbeiten, ihre Leistung nachverfolgen und Workflows optimieren können, hat es den internen Teams von Flo ermöglicht, die Deployment-Geschwindigkeit um über 900 %, die Durchlaufzeit um 88 % und die mittlere Problemlösungszeit um 99 % zu verbessern. Wir sind von einem massiven Release pro Monat zu 10 bis 20 Produktions-Deployments pro Tag übergegangen. Außerdem haben wir den durchschnittlichen Entwicklungszyklus von 5,8 Tagen auf 2,9 Tage und die Standardabweichung von 19,8 Tagen auf 3,5 Tage reduziert." Roman Bugaev CTO Ein Katalysator für Zusammenarbeit Schon zu Beginn stand Flo vor einer Reihe komplexer Herausforderungen. Einige sind für das Arbeitsgebiet des Unternehmens typisch. Es muss beispielsweise herausfinden, wie es Technologie für maschinelles Lernen mit den Gesundheitsdaten von echten Fachleuten kombinieren, oder den Datenschutz mit dem Aufbau einer Community vereinbaren kann. Flo hatte zudem mit Problemen zu kämpfen, von denen auch andere schnell wachsende Unternehmen in jeder Branche betroffen sind. Dazu gehören die Einführung moderner Praktiken, um die Geschwindigkeit und den Erfolg zu steigern, eine schnelle Skalierung ohne Einbußen bei der Vernetzung und Qualität sowie die Remote-Zusammenarbeit über weltweit verteilte Standorte hinweg. Für jede Herausforderung nutzte das Team die Cloud-Produkte von Atlassian, um an einer Lösung zu arbeiten. Da sich Flo der Innovation und Sicherheit verpflichtet fühlt, entschied sich das Unternehmen, die Arbeit in die Cloud zu verlegen. Das ISO/IEC 27001-Zertifikat von Atlassian überzeugte Flo davon, dass die Lösung in Sachen Datenschutz und Risikomanagement eine Hilfe sein würde. "Wir haben gebührende Sorgfalt walten lassen und sichergestellt, dass die Sicherheitsfunktionen, Datenschutzpraktiken und Betriebseigenschaften von Atlassian unsere Anforderungen erfüllen. Wir haben festgestellt, dass Atlassian Cloud eine zuverlässige und ausgereifte Lösung ist, auf die auch andere Unternehmen vertrauen. Durch das Arbeiten in der Cloud können wir uns verstärkt auf unsere Plattformen konzentrieren und müssen uns bezüglich Tools oder Wartung keine Gedanken machen", erklärt CTO Roman Bugaev. "Außerdem ist die Cloud dank Features wie Audit-Protokollen sicherer und zuverlässiger, was die Einhaltung von Vorschriften angeht. Wenn wir mit Atlassian arbeiten, können wir sicher sein, dass unser System ordnungsgemäß verwaltet wird. Eine Reproduktion derselben internen Umgebung würde uns viel Zeit und Ressourcen kosten. Diese investieren wir lieber in unser eigenes Produkt." Zu Beginn führte das Engineering Bitbucket Cloud für das Codemanagement, Confluence Cloud zum Speichern von Informationen und Jira Cloud – mit Add-ons wie Jira Misc Workflow Extensions – für eine effiziente, agile Produktentwicklung ein. Dank kostenloser Social-Media-Postings und interner Champions übernahm bald das ganze Unternehmen Atlassian-Lösungen, was den Austausch von Arbeitsergebnissen und Informationen zwischen Teams und Kunden deutlich einfacher machte. Von Entwicklern und Content-Autoren bis hin zu medizinischen Experten und Kundendienstmitarbeitenden – sie alle nutzen täglich eine Vielzahl von Atlassian-Produkten. Durch das Arbeiten in der Cloud können wir uns verstärkt auf unsere Plattform konzentrieren und müssen uns bezüglich Tools oder Wartung keine Gedanken machen. Außerdem ist die Cloud dank Features wie Audit-Protokollen sicherer und zuverlässiger, was die Einhaltung von Vorschriften angeht. Roman Bugaev CTO Aufbau einer Servicekultur mit verteilten Teams Die Teams bei Flo bauen gerade eine Servicekultur auf, die das gesamte Unternehmen umfasst – technische und nicht-technische Rollen sowie vor Ort und remote arbeitende Kollegen. Dabei dienen Atlassian-Lösungen als Grundgerüst, das eine höhere Effizienz und Effektivität unterstützen soll. Nicht-technische Teams wie die der Rechts- oder Compliance-Abteilung sehen beispielsweise in Jira Service Management nach, was zu tun ist, wenn Mitarbeiter entweder neu im Unternehmen anfangen, es verlassen oder eine andere Rolle übernehmen. Communications Manager Daria Grishechkina erzählt, dass ihr Team auch eine Reihe anderer Atlassian-Produkte verwendet, um mit wichtigen Stakeholdern im Unternehmen an der Erstellung von Inhalten zu arbeiten. Sie sagt: "Sämtliche Inhalte werden mehrmals von der Rechtsabteilung, von der medizinischen Abteilung und dem Produktmanagement korrigiert und bearbeitet. So wird sichergestellt, dass wir evidenzbasierte, vertrauenswürdige Informationen bereitstellen. Wir verwenden Atlassian für jeden Schritt – von der Erstellung über die Überprüfung bis hin zur Verbreitung." Die technischen Teams von Flo nutzen ihre integrierte Atlassian-Plattform auch, um mit anderen Abteilungen zusammenzuarbeiten und sämtliche Aspekte ihrer Arbeit zu optimieren. Das Engineering nutzt Jira Service Management nicht nur für das tägliche Produktmanagement und die agile Entwicklung, sondern auch um Serviceanfragen schnell zu verwalten, Warnungen zu überwachen und Bereitschaftspläne zu koordinieren – was bei so vielen verteilten Teams in verschiedenen Zeitzonen schwierig wird. "Wir hatten eine Überwachungslösung, aber wenn in Abwesenheit eine E-Mail eingeht, kann man auf diese nur schlecht reagieren", sagt Roman. "Es war eine wirklich gute Entscheidung, die Incident-Response-Funktionen von Opsgenie in Jira Service Management zu nutzen. Jetzt verfügen alle Produktentwicklungsteams über Servicedesks und Rotationspläne, die vorschreiben, wann sie Benachrichtigungen erhalten. Dadurch können wir schneller reagieren, wenn etwas schiefläuft." Dank des vernetzten, strukturierten Servicemanagement- und Warnsystems konnte Flo die mittlere Problemlösungszeit um 99 % reduzieren und die mentale Belastung senken. Beides hat die Arbeitsmoral der Mitarbeiter verbessert. "Früher mussten alle [für die Problembearbeitung] in Slack nachsehen. Jetzt haben es die Techniker mit den organisierten Workflows und Integrationen zwischen Jira Service Management und anderen Produkten deutlich einfacher. Sie sind weniger müde und haben mehr Spaß an der Arbeit", so Roman. "Dank der Atlassian-Tools und der gut organisierten und strengen Prozesse brauchen wir nicht mehr darüber nachzudenken, wie Aufgaben erledigt werden sollen. So können wir uns darauf konzentrieren, den Benutzern einen Mehrwert zu bieten." Roman fügt hinzu, dass Integrationen zwischen Jira Service Management, Jira, Bitbucket, Confluence und anderen wichtigen Tools im Workflow (einschließlich Slack, Snyk und SonarQube) die DevOps- und ITSM-Praktiken von Flo erleichtern. Marketplace-Apps wie Dynamic Forms und Extensions for Jira Service Management bieten noch mehr Kontext und Anpassungsmöglichkeiten, die Zeiteinsparungen bringen und Mitarbeitenden helfen, fundiertere Entscheidungen zu treffen. Beispielsweise arbeiten die IT-, die Entwicklungs- und die Sicherheitsabteilung mittels Atlassian-Tools zusammen, um Probleme zu lösen, Ursachen zu identifizieren und zukünftige Probleme zu verhindern. "Wir können die Problemursache einfacher erkennen, weil wir CI/CD-Pipelines haben, in denen wir alle Deployments sehen – nicht nur diejenigen, die mit Jira-Tickets verknüpft sind, sondern auch mit Confluence, Bitbucket und Slack verknüpfte Deployments", erklärt Roman. "Bitbucket ist in Slack integriert, sodass wir sehen können, wann eine Pipeline hinzugefügt wird. Und wenn sich ein Vorfall ereignet, lässt sich ganz einfach ein Slack-Channel erstellen, über den gemeinsam daran gearbeitet werden kann. In Opsgenie werden dann alle Vorfälle auf unserem Bildschirm angezeigt. Dadurch können wir Trends erkennen; entscheiden, ob Post-Mortem-Analysen angesetzt werden sollen, und Vorfälle mit Slack-Unterhaltungen verknüpfen, um den Verlauf nachzuverfolgen." Egal, ob mehrere Techniker gemeinsam ein Problem behandeln oder medizinische Experten, Produktentwickler und Content-Autoren sich über gesundheitliche Erkenntnisse austauschen – Atlassian ist der wichtigste Servicekanal, über den Informationen zwischen Teams und Benutzern übermittelt werden. "Atlassian bringt all diese Teams zusammen", sagt Roman. "Dank der benutzerfreundlichen Bedienoberfläche und der Integrationen können unsere medizinischen Experten schnell einsteigen und mit der Arbeit beginnen." Denn je schneller sie zu arbeiten anfangen, desto schneller können sie Positives für ihr Unternehmen und ihre Kunden bewirken. Die Techniker haben es mit den organisierten Workflows und Integrationen zwischen Jira Service Management und anderen Produkten deutlich einfacher. Sie sind weniger müde und haben mehr Spaß an der Arbeit. Roman Bugaev CTO Hier steht der Mensch on vorderster Stelle Aus dem einfachen Periodentracker von Flo ist eine fortschrittliche Gesundheits- und Wellness-App geworden und die Atlassian Cloud-Produkte haben sich mit dem Unternehmen weiterentwickelt. Während das Team seine Atlassian-Lösungen weiter ausbaute und integrierte, konnte Flo die Ergebnisse seiner harten Arbeit intern und in dem bereitgestellten Service nachvollziehen. "Wir sind in einem stark umkämpften Markt tätig, daher müssen wir möglichst effizient arbeiten. Wir automatisieren und optimieren viel mit Atlassian und dadurch können wir Engpässe in unserem Prozess reduzieren und unsere Ziele schneller erreichen", erklärt Roman. "Wir sind beispielsweise von einem massiven Release pro Monat zu 10 bis 20 Produktions-Deployments pro Tag übergegangen. Außerdem haben wir den durchschnittlichen Entwicklungszyklus von 5,8 Tagen auf 2,9 Tage und die Standardabweichung von 19,8 Tagen auf 3,5 Tage reduziert." Dank dieser Effizienz kann das Flo-Team nicht nur schneller arbeiten, es hat auch mehr Zeit und Energie übrig, um sich auf das Wesentliche zu konzentrieren. Roman sagt: "Unser großes, hoch gestecktes Ziel ist es, Frauen den Zugang zu Informationen zu ermöglichen, die sie brauchen, um ihre Gesundheit und sich selbst zu priorisieren. Bei uns sind alle Tools in einen nahtlosen Arbeitsbereich integriert. Das bedeutet, dass wir uns auf diese Mission und Produktziele konzentrieren können, anstatt darüber nachdenken zu müssen, wie wir Workflows organisieren oder was wir als Nächstes tun." Flo ist bereits auf dem besten Weg, dieses Ziel zu erreichen. Und seine bisherigen Erfolge feuern das Unternehmen an, seinen Weg weiterzuverfolgen. Mit einer stärkeren Vernetzung könnte das Unternehmen Flo einen wichtigen Beitrag dazu leisten, dass Menschen auf der ganzen Welt ein besseres Verhältnis zu ihrem Körper und ihrer Gesundheit entwickeln. Wenn du mehr über die Migration zur Cloud erfahren möchtest, besuche das Cloud Migration Center . Über Flo Branche Technologie Anzahl Benutzer Über 250 Standort Hauptsitz in London, England Atlassian-Produkte Bitbucket Git-Code-Management Confluence Das gemeinsame Bearbeiten von Dokumenten Jira Service Management IT Service Management für Teams Jira Flexibles Projektmanagement Atlassian Marketplace-Apps Extension for Jira Service Management Dynamic Forms Jira Misc Workflow Extension Cloud Weitere Informationen Check these out Einfachere Zusammenarbeit mit Jira Jedes Team unter einem Dach zusammenbringen Weitere Informationen Teste Atlassian Cloud noch heute Schneller Umstieg auf Atlassian Cloud Erste Schritte Wir präsentieren: Atlassian Rovo Mensch-KI-Kooperation bei jeder Aufgabe Jetzt testen Unternehmen Karriere Veranstaltungen Blogs Investor Relations Atlassian Foundation Presse-Kit Kontakt Produkte Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle Produkte anzeigen Ressourcen Technischer Support Kauf und Lizenzierung Atlassian Community Wissensdatenbank Marketplace Mein Konto Support-Ticket erstellen Lernen Partner Training und Zertifizierung Dokumentation Ressourcen für Entwickler Enterprise-Services Alle Ressourcen anzeigen Copyright © 2026 Atlassian Datenschutzrichtlinie Hinweis zur Sammlung von Daten Nutzungsbedingungen Impressum Deutsch ▾ window.SSR_detailMetrics=Object.freeze({"getFeatureGateValues":{"startTime":0,"duration":54},"fetchUserLocaleS2S":{"startTime":242,"duration":307},"initializeFeatureGatesClient":{"startTime":237,"duration":5},"resolveRoute":{"startTime":242,"duration":316},"resolvePageProps":{"startTime":558,"duration":20},"render":{"startTime":580,"duration":101}}); window.SSR_totalMetrics=Object.freeze({"startTime":1768296580372,"duration":681}); window.SSR_region="ap-northeast-2"; window.SSR_languagePack={"UserSeg.teamTypeSelection.customerService":"Kundenservice","UserSeg.teamTypeSelection.dataScience":"Data Science","UserSeg.teamTypeSelection.design":"Design","UserSeg.teamTypeSelection.finance":"Finanzen","UserSeg.teamTypeSelection.humanResources":"Human Resources","UserSeg.teamTypeSelection.itSupport":"IT-Support","UserSeg.teamTypeSelection.legal":"Recht","UserSeg.teamTypeSelection.marketing":"Marketing","UserSeg.teamTypeSelection.operations":"Operatives Geschäft","UserSeg.teamTypeSelection.otherOrPersonal":"Sonstiges","UserSeg.teamTypeSelection.productManagement":"Produktmanagement","UserSeg.teamTypeSelection.projectManagement":"Projektmanagement","UserSeg.teamTypeSelection.sales":"Vertrieb","UserSeg.teamTypeSelection.softwareDevelopment":"Softwareentwicklung","Jtbd.adhocTask":"Ad-hoc-Aufgaben- und Vorfallmanagement","Jtbd.backButton":"Zurück","Jtbd.chooseOptions":"Wähle bis zu 3 Optionen aus.","Jtbd.continueButton":"Weiter","Jtbd.createStrategies":"Strategien und Ziele erstellen","Jtbd.documentation":"Zentralisierte Dokumentation","Jtbd.header":"Wie möchte dein Team Jira nutzen?","Jtbd.launchCampaigns":"Kampagnen starten","Jtbd.manageBudget":"Budget und Ressourcen verwalten","Jtbd.manageClient":"Verwalten der Kunden- und Anbieterbeziehungen","Jtbd.manageMarketing":"Marketinginhalte verwalten","Jtbd.manageTasks":"Aufgaben verwalten","Jtbd.mapDependencies":"Abhängigkeiten von Aufgaben abbilden","Jtbd.prioritizeWork":"Priorisierung von Aufgaben","Jtbd.processRequests":"Anfragen von Stakeholdern bearbeiten","Jtbd.projectPlanning":"Projektplanung und -koordination","Jtbd.reportProgress":"Über den Projektfortschritt berichten","Jtbd.riskCompliance":"Compliance- und Risikomanagement","Jtbd.runSprints":"Sprints ausführen","Jtbd.subHeader":"Deine Auswahl schränkt deine Verwendungsmöglichkeiten nicht ein.","Jtbd.systemAudits":"System- und Tool-Evaluierungen","Jtbd.trackBugs":"Bugs verfolgen","Jtbd.workInScrum":"Vorgang in Scrum","TransparentTemplateV2.itSupport.productManagement.additionalInfo":"Du wirst zu Jira Product Discovery weitergeleitet. Du hast auf deiner Site weiterhin Zugriff auf Jira.","TransparentTemplateV2.itSupport.productManagement.poweredByText":"Wenn du \"Weiter\" auswählst, stimmst du der {customerAgreementLink} und {privacyPolicyLink} zu.","TransparentTemplateV2.itSupport.serviceManagement.additionalInfo":"Du wirst zu {productName} weitergeleitet und Service Collection wird bereitgestellt. Du hast auf deiner Site weiterhin Zugriff auf Jira.","TransparentTemplateV2.itSupport.serviceManagement.customerAgreementLink":"Atlassian-Kundenvereinbarung","TransparentTemplateV2.itSupport.serviceManagement.legalNotice":"Wenn du diese Vorlage auswählst, stimmst du den {customerAgreementLink} und {privacyPolicyLink} zu.","TransparentTemplateV2.itSupport.serviceManagement.poweredByText":"Unterstützt von","TransparentTemplateV2.itSupport.serviceManagement.privacyPolicyLink":"Datenschutzrichtlinie","sample-project.utils.approved-column-name":"Genehmigt","sample-project.utils.asset-issue-type-name":"Asset","sample-project.utils.bug-issue-type-name":"Bug","sample-project.utils.campaign-issue-type-name":"Kampagne","sample-project.utils.candidate-issue-type-name":"Kandidat","sample-project.utils.contact-issue-type-name":"Kontakt","sample-project.utils.default-kanban-project-name":"Mein Kanban-Projekt","sample-project.utils.default-scrum-project-name":"Mein Scrum-Projekt","sample-project.utils.done-column-name":"Erledigt","sample-project.utils.feature-issue-type-name":"Funktion","sample-project.utils.idea-column-name":"Idee","sample-project.utils.in-design-column-name":"Im Design","sample-project.utils.in-progress-column-name":"In Bearbeitung","sample-project.utils.in-review-column-name":"In Überprüfung","sample-project.utils.incident-issue-type-name":"Vorfall","sample-project.utils.live-column-name":"Live","sample-project.utils.request-issue-type-name":"Anfrage","sample-project.utils.research-item-issue-type-name":"Forschungsgegenstand","sample-project.utils.resolved-column-name":"Erledigt","sample-project.utils.service-request-issue-type-name":"Serviceanfrage","sample-project.utils.story-issue-type-name":"Story","sample-project.utils.support-issue-type-name":"Support","sample-project.utils.task-issue-type-name":"Task","sample-project.utils.testing-column-name":"Testen","sample-project.utils.todo-column-name":"Zu erledigen","sample-project.utils.user-testing-column-name":"UserTesting","sample-project.utils.waiting-for-customer-column-name":"WARTEN AUF KUNDEN","ConfluenceTemplatesCategoryDetailPage.pageTitle":"Kostenlose {title}-Vorlagen | Confluence","ConfluenceTemplatesCollectionDetailPage.pageTitle":"Kostenlose {title}-Sammlung | Confluence","ConfluenceTemplatesCollectionDetailPage.title-suffix":"Sammlung | Atlassian","Wac.Signup.PostOrder.Org.Setup.empty.page.administrationButton":"Zur Atlassian-Administration wechseln","Wac.Signup.PostOrder.Org.Setup.empty.page.header":"Es gibt keine berechtigten Organisationen für die Bereitstellung deiner Bestellung.","Wac.Signup.PostOrder.Org.Setup.empty.page.introBody":"Zeige deine bestehenden Organisationen in Atlassian-Administration an.","Wac.Signup.PostOrder.Org.Setup.empty.page.introBodyDescription":"Es ist möglich, dass alle deine Organisationen die Produkte bereits haben, oder du musst dich möglicherweise mit einem anderen Konto anmelden, das über Berechtigungen zur Bereitstellung verfügt.","Wac.Signup.PostOrder.CustomerManagedKeys.organization.card.alreadyEnabledCustomerManagedKeys":"Diese Organisation hat bereits Customer Managed Keys","Wac.Signup.PostOrder.Guard.organization.card.alreadyEnabledGuard":"Diese Organisation verfügt bereits über Guard","Wac.Signup.PostOrder.Rovo.organization.card.alreadyEnabledRovo":"Diese Organisation verfügt bereits über Rovo","Wac.Signup.PostOrder.Rovo.organization.card.select":"Auswählen","Wac.Signup.PostOrder.ServiceCollection.organization.card.alreadyEnabledServiceCollection":"Diese Organisation hat bereits Service Collection","Wac.Signup.PostOrder.Strategy.organization.card.alreadyEnabledStrategy":"Diese Organisation verfügt bereits über Strategy","Wac.Signup.PostOrder.Twc.organization.card.alreadyEnabledTwc":"Diese Organisation verfügt bereits über Twc","Wac.Signup.PostOrder.CustomerManagedKeys.organization.page.subtitle":"Wähle eine bestehende Organisation aus, um Customer Managed Keys zu nutzen.","Wac.Signup.PostOrder.Guard.organization.page.subtitle":"Wähle eine bestehende Organisation aus und starte Guard.","Wac.Signup.PostOrder.Rovo.organization.page.subtitle":"Wähle eine bestehende Organisation aus und starte eine Testversion von Rovo.","Wac.Signup.PostOrder.Rovo.organization.page.title":"Wähle eine Organisation aus.","Wac.Signup.PostOrder.ServiceCollection.organization.page.subtitle":"Wähle eine bestehende Organisation aus und starte Service Collection.","Wac.Signup.PostOrder.Strategy.organization.page.subtitle":"Wähle eine bestehende Organisation aus und starte Strategy.","Wac.Signup.PostOrder.TWC.organization.page.subtitle":"Wähle eine bestehende Organisation aus und starte TWC.","site-setup-header-order-confirmed-description":"Wir haben eine Bestätigungs-E-Mail gesendet an","site-setup-header-order-confirmed-title":"Deine Bestellung ist bestätigt.","site-setup-header-post-provisioning-description":"Du musst deine Site einrichten, bevor du dein Abonnement nutzen kannst.","site-setup-header-post-provisioning-title":"Erste Schritte","Wac.Signup.PostOrder.error.message":"Falls das Problem weiterhin besteht, wende dich mit der folgenden Trace-ID an den Support: {traceId}. ","Wac.Signup.PostOrder.error.title":"Wir sind uns nicht sicher, was schief gelaufen ist","Wac.Signup.PostOrder.PageLoading":"Wird geladen","JoinSiteUserDropdown.joinTeam":"Mein Team finden","JoinSiteUserDropdown.licenses":"Lizenzen","JoinSiteUserDropdown.logIn":"Einloggen","JoinSiteUserDropdown.logInAlternative":"Anmelden","JoinSiteUserDropdown.logOut":"Ausloggen","JoinSiteUserDropdown.logOutTriggerText":"Mein Konto","JoinSiteUserDropdown.profile":"Profil","JoinSiteUserDropdown.switchAccount":"Konto wechseln","globalNav.V2.navlink.lessMinus":"Weniger -","globalNav.V2.navlink.morePlus":"Mehr +","GlobalNav.RovoSection.Title":"KI-gestützte Apps – basierend auf dem Wissen deines Teams.","globalnav.v2.subnav.tabs.aria-label-tablist":"Produkte nach Benutzerkategorie","GlobalNav.collections.strategy.title":"Strategiesammlung","GlobalNav.collections.teamwork.title":"Teamwork Collection","GlobalNav.collections.strategy.tagline":"Leistungsstarke Apps optimieren die Strategie","GlobalNav.collections.teamwork.tagline":"Apps und Agenten fördern die Teamarbeit","globalnav.v2.pill":"Neu","globalnav.v2.products.featured.recommendations":"Empfohlen basierend auf deinen bestehenden Atlassian-Produkten","GlobalNav.collections.featured.featuredapps":"Vorgestellte Apps","GlobalNav.collections.featured.recommended.apps":"Empfohlen basierend auf deinen bestehenden Atlassian-Produkten","GlobalNav.collections.Title":"Atlassian-Sammlungen neu ","GlobalNav.collections.cloudplatform.heading":"Atlassian Cloud-Plattform","GlobalNav.collections.cloudplatform.mobilelabel":"Highlights","GlobalNav.collections.cloudplatform.tagline":"Die vernetzte Grundlage deines System of Work","GlobalNav.collections.featured.atlassiancollections.title":"Atlassian-Sammlungen","GlobalNav.collections.products.atlassiancloudplatform.cta":"Weitere Informationen","GlobalNav.collections.tagline":"Eine kuratierte Auswahl von Apps für deine spezifischen Anforderungen","GlobalNav.RovoSection.PoweredBy":"Unterstützt von","globalnav.treatment.pending":"(Ausstehende Übernahme)","globalnav.v2.products.bitbucket.description":"Quellcode und CI/CD","globalnav.v2.products.collectionservice.description":"Reaktionsschneller Service","globalnav.v2.products.collectionsoftware.description":"Schnelle Auslieferung hochwertiger Software","globalnav.v2.products.collectionstrategy.description":"Zuverlässige Optimierung von Strate | 2026-01-13T09:29:44 |
https://www.linkedin.com/checkpoint/rp/request-password-reset?session_redirect=%2Fproducts%2Fhubbedin-find-a-hiring-manager&trk=products_details_guest_primary_call_to_action | Reset Password | LinkedIn Sign in Join now Forgot password We’ll send a verification code to this email or phone number if it matches an existing LinkedIn account. Email or Phone We don’t recognize that email. Did you mean {:emailSuggestion} ? We’ll send a verification code to this email or phone number if it matches an existing LinkedIn account. Next or Back LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:44 |
https://git-scm.com/book/sl/v2/Veje-Git-Poteki-dela-z-vejami | Git - Poteki dela z vejami About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 3.4 Veje Git - Poteki dela z vejami Poteki dela z vejami Sedaj, ko imate osnove vej in združevanja, kaj z njimi lahko ali bi z njimi morali narediti? V tem razdelku bomo pokrili nekaj pogostih potekov dela, kar ta lahkotna razvejanja omogočijo, da se lahko odločite, ali bi jih želeli vkomponirati v vaš lastni razvojni cikel. Dolgotrajne veje Ker Git uporablja enostavno tri-načinsko združevanje, je združevanje iz ene veje v drugo večkrat skozi daljše časovno obdobje v splošnem enostavno. To pomeni, da imate nekaj vej, ki so vedno odprte in jih uporabljate za različne faze svojega razvojnega cikla; pogostokrat lahko združite iz nekaj njih v druge. Mnogi Git razvijalci imajo potek dela, ki zajema tak pristop, kot je imeti samo kodo, ki je v celoti stabilna v njihovi veji master — verjetno samo koda, ki je bila ali pa bo izdana. Imajo drugo vzporedno vejo imenovano develop ali next , iz katere delajo ali pa jo uporabljajo za testiranje stabilnosti — ni nujno vedno stabilna, vendar kadarkoli doseže stabilno stanje, se jo lahko združi v master . Uporabljena je za poteg tematskih vej (kratkotrajne veje, kot je vaša prejšnja veja iss53 ), ko so pripravljene, da se zagotovi, da prestanejo vse teste in ne povzročajo napak. V resnici govorimo o kazalcih, ki se premikajo navzgor po poti potrjevanj, ki jih delate. Stabilne veje so nižje na poti v vaši zgodovini potrditev in najnovejše veje so bolj na vrhu zgodovine. Slika 26. Linearni pogled progresivno stabilnega razvejanja V splošnem je o njih enostavnejše razmišljati kot o delovnih silosih, kjer skupki potrditev napredujejo k bolj stabilnim silosom, ko so v celoti testirani. Slika 27. Pogled »silosa« progresivno stabilnega razvejanja Tako delo lahko nadaljujete na mnogih nivojih stabilnosti. Nekateri večji projekti imajo tudi vejo proposed ali pu (angl. proposed updates ), ki ima integrirane veje, ki še niso pripravljene, da grejo v vejo next ali master . Ideja je, da so vaše veje na različnih nivojih stabilnosti; ko dosežejo stabilnejši nivo, so združene v vejo nad njimi. Ni treba imeti več dolgotrajnih vej, vendar je to pogostokrat koristno, posebej ko imate opravka z zelo velikimi in kompleksnimi projekti. Tematske veje Tematske veje na drugi strani so uporabne v projektih kakršnihkoli velikosti. Tematska veja je kratkotrajna veja, ki ste jo izdelali in jo uporabljate za posamezno določeno lastnost ali povezano delo. To je nekaj, česar verjetno še nikoli niste počeli z VCS prej, ker je v splošnem predrago izdelovati in združevati veje. Vendar v Gitu je pogosto izdelati, delati na, združiti in izbrisati veje nekajkrat na dan. To ste videli v zadnjem razdelku pri ustvarjanju vej iss53 in hotfix . Na njih ste naredili nekaj potrditev in jih takoj izbrisali po združitvi v glavno vejo. Ta tehnika vam omogoča kontekstni preklop hitro in v celoti — ker je vaše delo razdeljeno v nekaj silosov, kjer morajo biti vse spremembe v tej veji povezane z določeno temo, je enostavnejše videti, kaj se je zgodilo med pregledom kode in podobno. Tam lahko sledite spremembam nekaj minut, dni, ali mesecev in jih združite, ko ste pripravljeni ne glede na vrstni red, v katerem ste jih ustvarili ali delali na njih. Premislite o primeru, ko delate na nekem delu (na master ), razvejate za težavo ( iss91 ), delate ne njej nekaj časa, razvejate drugo vejo, da poskusite drug način upravljanja z isto stvarjo ( iss91v2 ), se vrnete na vašo vejo master in delate tam nekaj časa in nato razvejate, da naredite nekaj dela, za katero niste prepričani, če je dobra ideja (veja dumbidea ). Vaša zgodovina potrditev bo videti nekako takole: Slika 28. Več tematskih vej Sedaj recimo, da se odločite, da imate raje drugo rešitev za svojo težavo ( iss91v2 ); svojim sodelavcem ste pokazali vejo dumbidea in izkaže se, da je genialna. Originalno vejo iss91 lahko vržete stran (izgubite potrditvi C5 in C6 ) in jo združite v drugi dve. Vaša zgodovina je potem videti takole: Slika 29. Zgodovina po združitvi dumbidea in iss91v2 V večje podrobnosti o različnih možnih potekih dela za vaš Git projekt bomo šli v poglavju Porazdeljeni Git , tako da preden se odločite, katero shemo razvejanja bo vaš naslednji projekt uporabljal, se prepričajte, da ste prebrali to poglavje. Pomembno si je zapomniti, da ko delate vse to, so te veje v celoti lokalne. Ko razvejujete in združujete, je vse narejeno samo v vašem repozitoriju Git — ne dogaja se nikakršna komunikacija s strežnikom. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/%d0%9d%d0%b0%d1%87%d0%b0%d0%bb%d0%be-%d0%9a%d1%80%d0%b0%d1%82%d0%ba%d0%b0-%d0%b8%d1%81%d1%82%d0%be%d1%80%d0%b8%d1%8f-%d0%bd%d0%b0-Git | Git - Кратка история на Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 1.2 Начало - Кратка история на Git Кратка история на Git Като много велики неща в живота, Git започва с малко креативна разрушителност и ожесточени спорове. Linux ядрото е open source софтуерен проект от сравнително голям мащаб. В ранните години от поддръжката на проекта (1991-2002), промените в софтуера се изпращаха под формата на пачове и архивирани файлове. През 2002 г., Linux kernel проектът започна да използва патентована DVCS система наречена BitKeeper. През 2005, връзката между общността разработваща Linux ядрото и комерсиалната компания стояща зад BitKeeper се разпадна, след което инструментариума на BitKeeper вече не можеше да се ползва свободно. Това провокира общността от разработчици на Linux (и по-специално създателя му Линус Торвалдс) да разработи свой собствен инструмент за version control, базиран на част от знанията натрупани по време на използването на BitKeeper. Част от поставените цели и изисквания на новата система бяха както следва: Скорост Опростен дизайн Мощна поддръжка за нелинейна разработка (хиляди паралелни клонове код) Напълно разпределена работа Възможност да облужва ефективно големи проекти като Linux ядрото (по отношение на скорост и обем на данните) От създаването си през 2005 г. Git еволюира и узря така, че да е лесна за ползване и едновременно с това да поддържа първоначалните си цели описани по-горе. Git е впечатляващо бърза, ефективна с големи проекти и разполага с невероятна branching система за нелинейна разработка (виж Клонове в Git ) prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/ko/software/jira/service-management/enterprise | Jira Service Management Cloud Enterprise | Atlassian 콘텐츠로 건너뛰기 기능 가격 솔루션 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 리소스 유형별 ITSM 가이드 추가 리소스 자세히 보기 + 무료로 시작 무료로 시작 뒤로 무료로 시작 기능 가격 솔루션 리소스 로그인 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 유형별 ITSM 가이드 추가 리소스 무료로 시작 기능 가격 솔루션 리소스 로그인 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 유형별 ITSM 가이드 추가 리소스 Jira Service Management는 이제 Service Collection의 일부가 되어 그 어느 때보다 강력해졌습니다. Rovo, Assets 및 새로운 Customer Service Management 앱으로 탁월한 서비스 경험을 실현하세요. 지금 사용해 보기 Jira Service Management를 한 단계 끌어올리기 가장 진보된 Cloud 플랜인 Jira Service Management Enterprise는 규모에 맞는 안전하고 효과적인 팀워크를 지원합니다. 영업 팀에 문의 엔터프라이즈 확장을 엔터프라이즈 기회로 전환하세요 Jira Service Management Enterprise로 고급 보안, 확장, 분석 및 컴플라이언스를 확보하세요. 보안 확장성 분석 규정 준수 원활한 사용자 인증 Guard Standard로 가시성, 감사, ID 및 액세스 관리를 중앙 집중식으로 처리하세요. 사용자 관리 통합 자동 사용자 관리를 위해 여러 ID 공급자를 연결하여 여러 부서 및 지역을 관리하세요. 섀도 IT 추적 차단 앱 요청을 사용하여 새 사이트 요청을 검토하고 승인하세요. 모든 기능 및 가격 보기 리소스 Atlassian Guard 살펴보기 Guard를 통해 Atlassian Cloud 전반의 보안 및 가시성을 중앙 집중식으로 관리하는 방법을 확인하세요. 자세히 알아보기 Cloud Enterprise 보안 작동 방식 보기 Cloud Enterprise의 보안 컨트롤로 위험을 완화하는 방법을 알아보세요. 웹세미나 보기 Cloud Enterprise의 개요 보기 섀도 IT 컨트롤과 같은 Cloud Enterprise의 기능을 살펴보세요. 데모 보기 늘어나는 공간을 최적화 다른 워크플로에 영향을 주지 않고 새 팀 및 부서를 위한 여러 사이트를 설정하세요. 원활한 조직 관리 중앙 집중식 관리 및 청구를 사용하여 사용자 및 제품을 관리하고 제품별로 사용자당 한 번만 지불하세요. 변경 관리 프로세스 개선 업계 표준에 따라 사이트마다 여러 샌드박스를 사용하여 더 안전한 변경 관리 및 병렬 테스트를 수행하세요. 모든 기능 및 가격 보기 리소스 Cloud Enterprise에 대해 자세히 알아보기 Cloud Enterprise가 조직의 확장에 어떻게 도움이 되는지 알아보세요. 가이드 다운로드 여러 사이트 아키텍처 살펴보기 고객이 유연성 및 제어를 위해 여러 사이트를 어떻게 사용하는지 알아보기 전자책 받기 Atlassian 관리 작동 방식 보기 Cloud Enterprise 확장 컨트롤의 데모를 확인하세요. 데모 보기 도구 체인 전반에서 데이터를 연결 Atlassian Data Lake에 자사 개발자 데이터 및 타사 개발자 데이터를 통합하세요. 데이터 기반 의사 결정을 지원 변경, 인시던트 및 요청 관리 메트릭을 모니터링하여 서비스 블로커를 줄이고 AI 인사이트로 조치를 취하세요. Jira Service Management 데이터 확장 Atlassian 데이터를 자신의 환경 또는 비즈니스 인텔리전스 도구에 가져오세요. 모든 기능 및 가격 보기 리소스 규모에 맞는 의사 결정 속도 향상 즉시 사용할 수 있는 템플릿 및 사용자 지정 데이터 분석으로 데이터를 시각화하세요. 자세히 알아보기 DISH Network가 Cloud Enterprise로 성공하는 방법 확인 여러분과 같은 팀에서 Atlassian Analytics를 사용하여 가치를 창출하는 방법을 알아보세요. 녹화 시청하기 의사 결정의 수준을 높이는 방법 알아보기 Atlassian Analytics로 실행 가능한 인사이트를 추출하고 공동 작업을 개선하며 결과를 이끌어내세요. 웹세미나 보기 글로벌 컴플라이언스 환경 탐색 지역 및 산업별 컴플라이언스 표준을 준수하여 자신 있게 새로운 시장에 진출하세요. 모든 기능 및 가격 보기 리소스 Cloud Enterprise에 대해 더 자세히 알아보기 Cloud Enterprise가 특별한 이유를 자세히 알아보세요. 가이드 다운로드 Trust Center 살펴보기 컴플라이언스에 대한 Atlassian의 접근 방식을 알아보세요. 자세히 알아보기 Finoa가 Cloud Enterprise를 선택한 이유 보기 Finoa가 Cloud Enterprise를 사용하여 컴플라이언스 표준을 준수하는 방법을 알아보세요. 전문 보기 어떤 것도 놓치지 않는 고급 지원 선임 지원 에이전트 연중무휴(24/7) 지원 전화 지원 중요 이슈에 대해 30분 이내에 응답 Fortune 500대 기업 중 80% 이상이 신뢰 모든 고객 사례 살펴보기 “ Jira Service Management의 자동 알림, SLA 모니터링 및 사전 알림이 모두 Riverty에서 고객 지원 프로세스를 더 개선할 수 있었습니다. ” Andrei Tuch Atlassian 제품 소유자 Riverty의 스토리 읽기 “ Atlassian Cloud에 집중하고 거버넌스를 추가하여 도구 면에서 연간 250만 달러를 절약할 수 있다는 것을 알게 되었습니다. 연간 36%의 비용을 절감한 것입니다. 프로세스에는 도구 전반의 중복 사용자를 줄이고 더 많은 거버넌스를 적용하는 것이 수반될 것입니다. ” Emily Novak 제품 매니저, 디지털 작업 영역 및 솔루션 Rivian의 스토리 읽기 “ 추가 비용 없이 여러 사이트를 만들면 보안 목적으로 데이터를 분리하고 같은 솔루션으로 여러 사용 사례를 수용할 수 있습니다. 이는 애플리케이션 환경을 일치시키려는 저희의 아이디어에 완전히 부합합니다. ” Radoslav Danchev 협업, 작업 공간 및 지원 부문 부사장 Software AG의 스토리 읽기 고급 보안이 필요하십니까? Atlassian Guard Premium은 위협이 인시던트로 이어지기 전에 차단할 수 있도록 추가 보안 계층을 제공합니다. Atlassian Guard Premium에 대해 자세히 알아보기 Enterprise를 사용할 준비가 되지 않으셨습니까? Jira Service Management Premium은 엔터프라이즈만의 확장성 및 제어 없이 자산 관리, 고급 인시던트 관리 등을 제공합니다. Premium에 대해 자세히 알아보기 Jira Service Management Enterprise로 경쟁 우위를 더 향상 영업 팀에 문의 회사 채용 정보 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 연락처 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 모든 제품 보기 리소스 기술 지원 구입 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 만들기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2026 Atlassian 개인 정보 보호 정책 수집 시 알림 이용 약관 소유권 정보 한국어 ▾ | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%97%d0%b0%d0%bc%d0%b5%d1%81%d1%82%d0%b2%d0%b0%d0%bd%d0%b5 | Git - Заместване About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.13 Git инструменти - Заместване Заместване Както вече подчертахме, обектите в базата данни на Git са непроменими, но Git предлага интересен начин да се преструва , че замества обекти в базата си данни. Командата replace ви позволява да укажете един специфичен обект в Git и да кажете "всеки път, когато се обръщаме към този обект, третирай го като различен такъв". Това най-често е полезно за заместване на един къмит в историята с друг такъв без необходимост от преправяне на цялата история с git filter branch например. Нека кажем, че имате обширна история за даден проект и искате да я разделите на една по-кратка част за новите разработчици и една много по-дълга за хората, които искат да изследват кода в дълбочина. Можете да присадите едната история в другата "замествайки" най-ранния къмит в новата линия с най-късния от по-старата. Това е добре, защото означава, че в действителност не трябва да пренаписвате всеки къмит в новата история, което нормално бихте направили за да ги обедините в едно (защото наследствеността засяга SHA-1 хешовете). Нека да опитаме. Ще вземем налично хранилище, ще го разделим в две отделни, едно актуално и едно хронологическо и след това ще видим как с replace можем да ги комбинираме повторно без да модифицираме SHA-1 стойностите на новополучените. Използваме хранилище с пет кратки къмита: $ git log --oneline ef989d8 Fifth commit c6e1e95 Fourth commit 9c68fdc Third commit 945704c Second commit c1822cf First commit Искаме да разделим това на две линии история. Едната линия минава от къмити 1 до 4 - това ще ни е хронологическата линия. Втората линия ще е само с къмити 4 и 5 - това ще е актуалната история. Създаването на хронологическата линия е лесно, просто създаваме клон до точка в историята и след това го публикуваме в master клона на ново отдалечено хранилище. $ git branch history c6e1e95 $ git log --oneline --decorate ef989d8 (HEAD, master) Fifth commit c6e1e95 (history) Fourth commit 9c68fdc Third commit 945704c Second commit c1822cf First commit Сега можем да публикуваме новия history клон към master клона в новото ни хранилище: $ git remote add project-history https://github.com/schacon/project-history $ git push project-history history:master Counting objects: 12, done. Delta compression using up to 2 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (12/12), 907 bytes, done. Total 12 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (12/12), done. To git@github.com:schacon/project-history.git * [new branch] history -> master Така историята ни е публикувана. По-трудната част е да орежем актуалната си история, така че да стане по-кратка. Трябва ни обща пресечна точка (общ къмит), такава в която да можем да заменим къмит от едната линия с къмит в другата. Ето защо ще отрежем историята до два къмита - четвърти и пети (така че къмит 4 да е общ за двете страни). $ git log --oneline --decorate ef989d8 (HEAD, master) Fifth commit c6e1e95 (history) Fourth commit 9c68fdc Third commit 945704c Second commit c1822cf First commit В този случай е полезно да създадем base къмит с инструкции за това как да се разшири историята, така че другите разработчици да знаят какво да правят ако срещнат първия къмит в съкратената история и се нуждаят от по-старите. Така че, това което ще направим, е да създадем начален къмит играещ ролята на изходна точка с инструкциите, след което да пребазираме останалите два къмита (четвърти и пети) върху него. За да започнем, трябва да изберем точка за разделяне, която за нашия случай ще е в третия къмит, 9c68fdc . Така base къмитът ни ще бъде базиран на това дърво. Можем да го създадем с командата commit-tree , която просто приема дърво и ще ни върне SHA-1 хеша на един нов къмит без родители. $ echo 'Get history from blah blah blah' | git commit-tree 9c68fdc^{tree} 622e88e9cbfbacfb75b5279245b9fb38dfea10cf Забележка Командата commit-tree е една от командите в Git известни като 'plumbing' команди. Това са команди предназначени за индиректно използване с други Git команди за извършване на по-малки дейности. В случаи като този, в който извършваме необичайни дейности, тези команди ни дават средства от по-ниско ниво, но като цяло не се използват в ежедневната работа. Повече за plumbing командите ще видим в Plumbing и Porcelain команди . Сега имаме базов къмит и можем да пребазираме остатъка от историята ни върху него с git rebase --onto . Аргументите към --onto ще бъдат SHA-1 стойността, която получихме от commit-tree , както и точката на пребазиране, тоест третия къмит (родител на този, който искаме да пазим, 9c68fdc ): $ git rebase --onto 622e88 9c68fdc First, rewinding head to replay your work on top of it... Applying: fourth commit Applying: fifth commit Сега пренаписахме актуалната история базирайки я на начален къмит съдържащ в себе си инструкции за това как да реконструираме цялата история, ако поискаме това. Можем да публикуваме тази история в нов проект и когато хората клонират това ново хранилище те ще видят само последните ни два къмита и базов къмит с инструкции. Нека сега се поставим на мястото на тези хора и да видим как можем да се сдобием с пълната история на проекта. За да вземем хронологическите данни след клонирането на това орязано хранилище, трябва да добавим втора отдалечена референция към хронологическото хранилище и да изтеглим: $ git clone https://github.com/schacon/project $ cd project $ git log --oneline master e146b5f Fifth commit 81a708d Fourth commit 622e88e Get history from blah blah blah $ git remote add project-history https://github.com/schacon/project-history $ git fetch project-history From https://github.com/schacon/project-history * [new branch] master -> project-history/master Сега актуалните къмити са в клона master а хронологичните в project-history/master . $ git log --oneline master e146b5f Fifth commit 81a708d Fourth commit 622e88e Get history from blah blah blah $ git log --oneline project-history/master c6e1e95 Fourth commit 9c68fdc Third commit 945704c Second commit c1822cf First commit За да ги комбинираме, можем да изпълним git replace с къмита, който искаме да заместим и този, с който искаме да го заместваме. Ние искаме да заменим "fourth" къмита в master клона с "fourth" къмита от project-history/master : $ git replace 81a708d c6e1e95 Сега, ако прегледаме историята на клона master , тя е подобна: $ git log --oneline master e146b5f Fifth commit 81a708d Fourth commit 9c68fdc Third commit 945704c Second commit c1822cf First commit Изглежда наистина много добре, защото без да се налага да променяме цялата SHA-1 верига успяхме да заместим един къмит от историята с изцяло друг къмит и всички нормални инструменти (като bisect , blame ) ще работят както бихме очаквали от тях. Обаче, историята все още показва 81a708d като SHA-1 стойност, въпреки че реално се използват данните от c6e1e95 с който заместихме. Дори ако изпълните команда като cat-file , тя ще ви покаже заменените данни: $ git cat-file -p 81a708d tree 7bc544cf438903b65ca9104a1e30345eee6c083d parent 9c68fdceee073230f19ebb8b5e7fc71b479c0252 author Scott Chacon <schacon@gmail.com> 1268712581 -0700 committer Scott Chacon <schacon@gmail.com> 1268712581 -0700 fourth commit Спомнете си, че действителният родител на 81a708d беше нашия placeholder къмит ( 622e88e ), а не 9c68fdce както се твърди. Друг интересен момент е, че тази информация се пази в референциите ни: $ git for-each-ref e146b5f14e79d4935160c0e83fb9ebe526b8da0d commit refs/heads/master c6e1e95051d41771a649f3145423f8809d1a74d4 commit refs/remotes/history/master e146b5f14e79d4935160c0e83fb9ebe526b8da0d commit refs/remotes/origin/HEAD e146b5f14e79d4935160c0e83fb9ebe526b8da0d commit refs/remotes/origin/master c6e1e95051d41771a649f3145423f8809d1a74d4 commit refs/replace/81a708dd0e167a3f691541c7a6463343bc457040 Това означава, че е лесно да споделим подмяната си с други хора, защото можем да я публикуваме в сървъра ни и те лесно могат да я свалят. Това не е така полезно в сценария, който следвахме тук (понеже така или иначе всеки ще изтегля и двете истории и е излишно да ги разделяме), но може да е полезно в други ситуации. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/api/request-signing.html | Request Signing | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Developer API Request Signing Request Signing Use your account's API key to authenticate requests with Reflect . Request Signing To access the Reflect API, you must sign all requests using your API key . API keys are associated with your account, not your user, which means that all users of your account will share the same API key. For every API request, an X-API-KEY request header must be populated with your API key. To view your API key, navigate to Settings > Account Information , and scroll to the “API Access” section. In this section : Request Signing Request Signing Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/integrations/test-case-management.html | Test Case Management | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations Test Case Management Test Case Management Automatically sync Reflect tests and test results to your existing Test Case Management tool. With Reflect ’s test case management integrations, testing teams can adopt Reflect without disrupting their current process around test execution reporting and defect tracking. Installation To connect Reflect to your test case management tool, navigate to the Settings section within Reflect and select the Integrations tab. Our supported integrations for TestRail , Xray and Zephyr (formerly TM4J) are shown under the Test Case Management section : TestRail ENABLING THE TESTRAIL API Reflect ’s integration with TestRail requires that the TestRail API first be enabled for your account. Within TestRail, verify that the TestRail API is enabled by clicking on the Administration tab, selecting the Site Settings section, and clicking the API tab. Under API, the Enable API option should be checked. If it is not, enable this option and click the Save button to enable the API. GENERATING AN API KEY Within TestRail, click on your name in the upper right corner of the page and select My Settings . Under My Settings , select the API Keys tab. On this page you will see a list of the existing API Keys associated with your TestRail user, along with an option to add a key. We recommend creating a dedicated API Key for Reflect . To create an API key, click the Add Key link, give your API key a relevant name, and click Generate Key. A new API key will be generated and displayed on the screen. CONNECTING TO TESTRAIL Within Reflect , navigate to Settings and click on the Integrations link on the left navigation bar. Find the TestRail integration and click the Connect button. You will be prompted to enter the following fields to connect to TestRail: Username: The username or email address that you use to log into TestRail. Example: [email protected] Hostname: The hostname of your TestRail instance. Note that the hostname should NOT include http:// or https://. Example: acmecorp.testrail.io API Key : The TestRail API key that you generated by following the steps in the previous section. TestRail Project : The Project within TestRail that should contain all of the Test Cases and Test Runs associated with your Reflect tests. Linking to Test Cases and Test Runs across projects is not supported. TestRail Suite: The Suite within TestRail that contains all of the Test Cases and Test Runs associated with Reflect . If you do not use Suites within TestRail, select the Master option. Linking to Test Cases and Test Runs across suites is not supported. After saving your settings, you should see that the TestRail integration is connected: Xray Generating a Client ID and Client Secret In order to connect Reflect to Xray, you’ll need to generate an API key within Jira and save the generated Client ID and Client Secret in Reflect . To generate an API key, follow the steps in these instructions provided by Xray: https://docs.getxray.app/display/XRAYCLOUD/Global+Settings%3A+API+Keys . Connecting to Xray Within Reflect , navigate to Settings and click on the Integrations link on the left navigation bar. Find the Xray integration and click the Connect button. You will be prompted to enter the following details: Client ID : The Client ID generated in Xray using the steps outlined in the previous section. Client Secret : The Client Secret generated using the steps from the previous section. Project: The Jira project that contains your Xray tests. Creating tests across Jira projects is not supported. Test Case Issue Type: The Jira issue type that’s used to represent an Xray test. This is usually named Test. Test Execution Issue Type: The Jira issue type that’s used to represent an Xray test execution. This is usually named Test Execution. Note Jira must first be connected to Reflect before connecting Xray. After saving your settings, you should see that the Xray integration is connected: Zephyr GENERATING AN ACCESS TOKEN Reflect authenticates with the Zephyr API using an Access Token that you generate within the Zephyr UI. To generate an access token, navigate to Zephyr, click your avatar on the top right, and select the Zephyr API Access Tokens menu item. On the following page, click the Create access token button to generate a new token. See API Access Token Management . CONNECTING TO ZEPHYR Within Reflect , navigate to Settings and click on the Integrations link on the left navigation bar. Find the Zephyr integration and click the Connect button. You will be prompted to enter the following details: Access Token. The Access Key generated in Zephyr using the steps outlined in the previous section. Project. The Jira project that contains your Zephyr tests. Creating tests across Jira projects is not supported. After saving your settings, you should see that the Zephyr integration is connected: Linking Test Cases In order for test results to be synchronized to your test case management tool, you must first map tests within Reflect to their associated test cases from your test case management tool. When a Reflect test is associated with a test case in your test case management tool, a link will appear on Reflect ’s test detail page: Manually mapping test cases After connecting your test case management tool using the instructions above, you can map Reflect tests to existing test cases by navigating to the Integrations section under Settings and clicking the Assign Tests button. A modal will appear which displays the current mappings between Reflect tests and your connected test management tool: To assign an existing test case to a Reflect test, click on the dropdown and start typing the test case name in the typeahead search input. The test case should be displayed along with its associated key/id. Select the test case to update the mapping. After you’ve made your mapping updates, click the Save Mappings button to save your changes. Automatically generating test cases When creating new tests in Reflect , you’ll also have the option to automatically generate an associated test case for that test in your test case management tool. When the test is created, Reflect will generate a test case that contains the test steps from the newly created test, and will automatically map the new test case to your Reflect test. This option can be configured to be enabled or disabled by default within the Settings modal on the Integrations page, and can be overridden before saving your new test. Syncing test results With your test case management tool connected, and your Reflect tests mapped, test results will now automatically start syncing to your test case management tool. Specifically, the results of all Suite Executions within Reflect will be synchronized through the creation of the following, depending on your tool: TestRail : A Test Run is created that contains a collection of Results. Xray : A Jira Issue with the specified Test Execution issue type is created that contains a collection of Test Runs . Zephyr Essential and Zephyr : A Test Cycle is created that contains a collection of Executions . After the Suite Execution completes, a link is displayed in the header which links to the results in the test case management tool: In this section : Test Case Management Installation TestRail Xray Zephyr Linking Test Cases Manually mapping test cases Automatically generating test cases Syncing test results Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/manage-tests/folders.html#changing-a-test-s-folders | Folders | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Folders Folders Group related tests together in lightweight collections. Folders are a lightweight way to group a set of tests together. Managing Folders The Test List view on the Reflect main screen shows a list of all folders on the left side and a table of tests within the selected folder on the right. All accounts have at least one folder, the “All Tests” folder, which cannot be removed or renamed. You can create a new folder by clicking the “Add Folder” link at the bottom of the folders list. To rename a folder, click the pencil icon next to the folder name at the top of the Test List view. To delete a folder, click the “Delete Folder” button and accept the confirmation dialog. Changing a Test’s Folders You can modify the folders that contain a test from the Test Detail page. You can add a new folder within this view as well. In this section : Folders Managing Folders Changing a Test’s Folders Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://www.atlassian.com/zh/software/jira/templates/it-operations | IT Operations Templates | Jira Template Library | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Jira 模板 Open and close the navigation menu 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 免费获取 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 IT operations templates Connect ops managers, devs, and site reliability engineers with Jira Service management. Empower teams with full context around changes and bring them together to resolve incidents when they happen. IT 服务管理 承接请求、设置警报、提起事件并快速修复问题。 高级 IT 服务管理 运用 ITSM 最佳实践管理事件、变更和问题。 客户服务管理 向外部客户提供卓越的服务体验。 分析服务管理 管理员工对其所需数据和洞察信息的请求。 Successful teams use IT operations templates "The organized workflows and integrations between Jira Service Management and other products make it much easier for engineers. They are less tired and enjoy the work more." Roman Bugaev Chief Technology Officer, Flo IT operations resources Jira Service Management for IT Ops An easy-to-use solution that brings software development and IT onto the same platform to deliver and manage services. 了解更多 Jira Service Management 产品指南 如何使用 Jira Service Management：指南、教程和演示。 查看指南 Jira Service Management 演示 选择您感兴趣的特定功能，我们可为您提供个性化演示。 观看演示 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/manage-tests/editing---re-recording.html#restoring-a-previous-version | Editing / Re-Recording | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Editing / Re-Recording Editing / Re-Recording Configure the assertions and validations in your test, and modify test steps directly in-line. Reflect ’s philosophy on automated regression tests is that “coding” or “scripting” front-end tests is tedious and error-prone. As a result, Reflect does not support creating tests this way, and instead, derives test definitions automatically from instrumenting normal user web sessions. This eliminates some forms of user-error, which can lead to false positive test failures, and it produces a more consistent test definition, which fosters more efficient test execution. An added benefit is that anyone in your organization can create and manage tests. Of course, it can be just as tedious to have to re-create a test from scratch when all you need is to modify one test step. Thus, Reflect supports several methods of editing an existing test, but does so in a way that is still rooted in Reflect ’s cloud-based browser, rather than coding. All forms of test editing are available from the Test Detail page, while test configuration such as changing folders and adding a description can be done from the test definition page. Accepting Changes A simple way to modify a test definition is to accept the current state of the page’s content in place of what was recorded. This most often occurs when a test is failing a Visual Validation test step due to the visual state or text content not matching what’s expected. The natural evolution of a page’s content means that there will be legitimate changes in expected content over time, and Reflect makes it easy to accept these changes as the new baseline assertion values for the test. To accept changes for a Visual Validation or other test step, click the test step to open its Test Step Detail view. From there, inspect the actual content displayed on the page compared to the baseline. If the actual content is correct, click “Accept Changes” in the specific sections. After clicking “Accept Changes”, a Save button will appear at the bottom of the test definition panel. Click the Save button to save the accepted changes. Input Changes If your test includes steps for entering text into the page under test, you can alter this input text from the Input Text section on the Test Step Detail view. Whether it’s an input element or textarea , the detail view is editable and accepts changes directly in-line. As with other edits, you’ll need to click the Save button when you are finished editing the text in order to save the edits to the test definition. It’s important to remember that changing the input values in your test may result in subsequent test actions being invalid depending on how the new input values change the webpage. As before, click Save to save the changes to your test definition and trigger a new test execution. Delete a Test Step To delete a step from a test, click on the test step to open the Test Step Detail view. Scroll to the bottom of the panel and click Delete Step . Multiple steps can be deleted at once by clicking the checkboxes in the left sidebar next to the test steps you wish to delete, and clicking the Delete Steps option in the toolbar that appears at the top of the page. Re-recording a Test The most flexible way to modify a test’s definition is to re-record the test through Reflect ’s interactive test editor. Re-recording allows you to insert or delete test steps anywhere in the test definition without repeating actions that you have already recorded. Initiate the interactive test editor by hovering between the two steps where you wish to insert new step(s), and click the option Re-record from this point . This will navigate your browser to the regular Recording experience, except your existing test definition will already be populated on the left sidebar. The Reflect cloud browser will execute the test definition up until the test step that you previously selected. When playback is complete, Reflect will enable the browser for recording and begin capturing your actions and inserting them into the test. When you have finished inserting new test actions, click “Resume Execution” to watch Reflect continue the execution of the test definition from the current location. In some cases, you may wish to re-run a subset of test steps before saving the test. To do so, either click and drag the “execution pointer” to the desired location, or hover between the steps you wish to move it to and click “Move execution pointer”. If the new location is earlier in the test, Reflect will automatically insert a breakpoint at the previous location. If you wish to interact with the browser session without recording additional steps, click the Recording checkbox in the top right of the browser window. Additional steps will not be recorded when the Recording checkbox is deselected. When the test has completed, or if you simply wish to save the updated definition and leave, you can click “Save”. Reflect will continue the execution of your test to its conclusion (if it’s not already there), and then save a test run for the updated definition. You can always end the re-recording session without saving any changes by clicking “Exit” or “Exit without Saving”. Note Test runs produced from a re-recording session do not count towards the billing cycle execution hours. Watch Live When Reflect is executing a test, you have the option to watch the test run live via the “Watch Live” button that appears wherever the test run is displayed in Reflect . Clicking this button will take you to the same interactive editor and viewer that is used when re-recording. This means that in addition to watching the test execute, you can also pause and edit the test. Interactive Editing During a re-recording or when watching a test run live, it’s possible that steps in the original test definition will fail during playback when the Reflect test executor tries to perform them. By default, the executor will retry a failing step for up to 30 seconds before failing the test. During a re-recording session, Reflect allows the user to interrupt the retry process and take corrective action manually. When the executor begins retrying the test step, you’ll see a banner at the top of the recording session indicating the retry attempt. Click “Stop Retrying” to interrupt the execution, or you can wait for the retry timeout to elapse (e.g., 30 seconds). Then, Reflect will display contextual information describing the failed test step. From here, you can select the best option for fixing the failing test step. Often, you will want to click “Replace Step” to re-enable the recording experience and overwrite the failing test step with newly-recorded steps. Alternatively, if the failing test step is erroneous, you can delete it outright and resume execution. If the failing test step is a Visual Validation, you can click “Use latest visuals” to explicitly update the text and baseline image to the live values. If the failing test step is a Text Validation, the “Use latest text” option will let you update the step to use the latest text value. Copying a Test If you have a test that you don’t want to change, but you want to reuse some or all of the test’s existing test steps in a new test, you can use the “Make a Copy” feature. Since a Reflect test is defined by the sequence of test step actions, making a copy is a lightweight operation that creates an independent logical test with exactly the same test steps as the original. You can then execute, modify and delete the copied test without any impact to the original test. From the test definition page, click on the button with the three dots on the top right of the page, and then click “Make a Copy” within the dropdown menu: After making a copy, you’ll be redirected to the test definition page for the newly-created test. From there, you can execute the test (with the “Run Test” button), or modify the test definition, including through the re-recording feature described above. Restoring a Previous Version Reflect stores each version of a test’s definition independently, and associates each test run with a specific version of the test. The test definition page lists all historical runs for a test. You can update, or revert, a test’s definition to use a prior definition by clicking “Restore this Version” from the context menu on a previous test run. Reflect does not immediately execute the test after restoring a previous version. This allows you to re-record from a specific step from the updated definition in the left sidebar, or otherwise edit the test before executing it. To run the restored test definition, click “Run Test”. In this section : Editing / Re-Recording Accepting Changes Input Changes Delete a Test Step Re-recording a Test Watch Live Interactive Editing Copying a Test Restoring a Previous Version Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT0I3zGm9Xl4HX6B-S9tUcR8Y7xs_F_zt8Vk5e7-zJIrowx-Z8D43DOQZ9Tud7kpEU1LxWcSHu1Fc1VYTu6zNeWMDi1SVx3OI0Xcrq5oYtsuxtrb606AETE59DIfsn009ppuERJo1LdwXSJ3 | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:44 |
https://www.digitalcameraworld.com/tag/ibc | IBC 2026 News, Features and Coverage | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . IBC Latest about IBC The Nikon ZR is just the start! Nikon insiders reveal plans for future Nikon x Red video cameras and a new line of Z Cinema lenses By Adam Waring last updated 16 September 25 News Digital Camera World grilled Nikon’s top brass about the development of the Nikon ZR compact cine camera and what's next for the Red Z Cinema colab, and this is what they had to say… News An AI autofocus adapter that gives us expanded focusing capabilities? Viltrox makes headlines at IBC 2025 By Kim Bunermann published 12 September 25 NEWS Viltrox's AI-powered autofocus adapter could change how we shoot with lenses – here's what we know NEWS Viltrox unveils IBC lineup: Four new lenses, a TTL flash and the first all-new Evo series optic By Kim Bunermann published 12 September 25 NEWS Smart design, fresh optics and a flash with attitude – VIltrox brings serious updates to IBC 2025 NEWS IBC 2024: Camera news and product launches from the giant industry event By James Artaius last updated 16 September 24 IBC 2024 The broadcasting industry's biggest event of the year is taking place in Amsterdam right now – here's what's happening at IBC 2024 IBC 2024 I just saw these new, unannounced Thypoch cine lenses at IBC By Gareth Bevan published 13 September 24 NEWS Thypoch is showing off its teased cine lenses at IBC in Amsterdam – and I got my hands on them NEWS Blackmagic unveils Ursa 17K 65mm camera to tackle Arri – but it costs $29,995 By Sebastian Oakley published 13 September 24 News The 17K, 65mm large format camera from Blackmagic comes with a similarly large $29,995 price tag News Adobe Premiere Pro makes color grading a cinch with simpler way to RAW and Log video editing By Tom May published 11 September 24 news Everyone in video production is stressed, so these new editing features are aimed to save you time and energy. news Canon launches EOS C80 full-frame cinema camera By Gareth Bevan published 9 September 24 NEWS Canon's newest 'budget' RF-mount pro video camera NEWS Atomos unleashes new Shogun 6K and 8K RAW monitors in October By Kalum Carter published 24 September 23 News Atomos is launching a new generation of 6K and 8K RAW Shogun monitors next month News IBC 2023: news and rumors of the anticipated products and launches By James Artaius, Chris George last updated 12 September 23 IBC 2023 The industry's biggest event for broadcast imaging is back in Amsterdam this week – here's what to expect from IBC 2023 IBC 2023 1 2 Archives Get the Digital Camera World Newsletter The best camera deals, reviews, product advice, and unmissable photography news, direct to your inbox! Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. LATEST ARTICLES 1 OWC launches the ultimate portable SSD 2 Meet the wildlife photographer buying up land in Africa to protect animal habitats, using money he makes with his camera 3 The secret meaning behind the name Minolta (and how the camera brand evolved before disappearing forever) 4 Meet the youthful, often shocking future of fine art photography at Circulation(s) 2026 5 How will you fare in my photography general knowledge quiz? Digital Camera World is part of Future US Inc, an international media group and leading digital publisher. Visit our corporate site . Add as a preferred source on Google Terms and conditions Contact Future's experts Privacy policy Cookies policy Advertise with us About us Accessibility Statement Careers © Future US, Inc. Full 7th Floor, 130 West 42nd Street, New York, NY 10036. Close Please login or signup to comment Please wait... Login Sign Up | 2026-01-13T09:29:44 |
https://aws.amazon.com/aurora/ | Relational Database – Amazon Aurora MySQL PostgreSQL – AWS Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Amazon Aurora Overview Engines Features Pricing Resources More Databases › Amazon RDS › Amazon Aurora Try Aurora for free with AWS Free Tier Amazon Aurora Unparalleled high performance and availability at global scale for PostgreSQL, MySQL, and DSQL Get started with Aurora Connect with an Aurora specialist Why Aurora Aurora has 5x the throughput of MySQL and 3x of PostgreSQL with full PostgreSQL and MySQL compatibility. Aurora also offers DSQL, the fastest distributed SQL database that is PostgreSQL-compatible. Aurora is designed for up to 99.999% multi-Region availability. With Aurora DSQL, Aurora provides virtually unlimited scale in and across regions with no infrastructure management. Aurora offers broad compliance standards and enterprise security capabilities, and support for globally distributed apps. Play Benefits of Aurora High performance Power internet-scale applications with 5x the throughput of MySQL, 3x of PostgreSQL, and the fastest distributed SQL reads and writes with Aurora DSQL. Learn more High availability Designed for up to 99.99% single-Region and 99.999% multi-Region availability with fault-tolerant distributed storage to ensure continuous data access and durability for your applications. Learn more Scale and build with ease Automatically scale to the demands of any workload, removing bottlenecks while maintaining performance. Learn more Cost-effective Improve productivity and lower total cost of ownership with a fully managed database including innovations like serverless so you can focus on building applications that delight your users. Learn more Easy to migrate Easily migrate MySQL or PostgreSQL databases to and from Aurora using standard tools, or run legacy SQL Server applications with Babelfish for Aurora PostgreSQL with minimal code change. Learn more Use cases Modernize enterprise applications Operate enterprise applications, such as customer relationship management (CRM), enterprise resource planning (ERP), supply chain, and billing applications, with high availability and performance. Build SaaS applications Support reliable, high- performance, and multi-tenant Software-as a-Service (SaaS) applications with flexible instance and storage scaling. Deploy globally distributed applications Develop internet-scale applications, such as mobile games, social media apps, and online services, that require multi-Region scalability and resilience. Go serverless Hands-off capacity management, and pay only for capacity consumed with instantaneous and fine-grained scaling to save up to 90% of cost. Next Steps Resources Learn with hands-on training Get started with Aurora Documentation Dive deep on Aurora Read the documentation Free tier Sign up for a free account Try for free Console Start building in the console Sign in Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:44 |
https://www.linkedin.com/products/hubbedin-find-a-hiring-manager?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in#main-content | Find a Hiring Manager | LinkedIn Skip to main content LinkedIn HubbedIn in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Find a Hiring Manager AI-Powered Coaching Software by HubbedIn See who's skilled in this Add as skill Try now Report this product About Our "Find Hiring Manager" tool is designed to significantly enhance your job search. We leverage AI to connect you directly with hiring managers, giving you the edge you need to stand out. By providing access to the email and LinkedIn profiles of hiring managers, we help you reach the right people faster. Our platform also crafts personalized messages by analyzing your resume and the job details, increasing your chances of getting hired. Plus, with our resume builder's tracker feature, you can stay informed about your resume's performance. Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software AI Resume Builder AI Resume Builder AI-Powered Coaching Software CoachHub - The digital coaching platform CoachHub - The digital coaching platform AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Sign in to see more Show more Show less HubbedIn products AI Resume Builder AI Resume Builder AI-Powered Coaching Software AI Video Interviewer AI Video Interviewer Video Interview Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:44 |
https://apps.apple.com/app/apple-store/id1006972087 | Jira Cloud by Atlassian App - App Store for iPhone iPhone iPad Mac Vision Watch TV Today Games Apps Arcade Platform iPhone iPad Mac Vision Watch TV Jira Cloud by Atlassian Track tasks, projects & work Free Share 36K Ratings 4.7 Ages 4+ Years Category Productivity Developer Atlassian Language EN + 26 More Size 407.9 MB iPhone, iPad Stay productive, no matter where you are or what team you’re on. Jira, the #1 agile project management software, serves every team from engineering to marketing. Jira Mobile gives you instant, on-the-go access to all your work items, team projects, and updates. Download the app and see why 300,000+ organizations plan and track work in Jira. KEEP MOVING WORK FORWARD • Create, update, and edit work from bugs to campaigns • Attach files and leave comments for team context • Plan, track, and analyze with roadmaps and reports NEVER MISS AN UPDATE • Get real-time push notifications • Decide what you want to be notified about • Snooze notifications or set working hours for focus CHECK PROJECT PROGRESS • See key metrics at a glance with project summaries • Track project progress and priorities • Identify issues quickly to make fast decisions MANAGE TEAM REQUESTS • Create and customize forms and report issues easily • Submit requests for creative, content, inventory, and more • Streamline task assignment for your team APPROVE & UNBLOCK WORK • Review and approve work items on the go • Assign reviews to the right users • Create a consistent and efficient review process Download the app and create an account for free. Jira users can log in using their existing Jira details. Got questions? Our support team is here to help! more Ratings & Reviews 4.7 out of 5 36K Ratings Please add This feature to roadmap 04/30/2023 Agent619 Hi and thanks for the great app. I would really love to make Jira mobile a huge part of my planning process. It’s great for quick touch ups and reference glances or just knocking things out. There’s just a small thing that I want a little more on the roadmap.I want to be able to see the linked items per epic. When I’m on desktop, I can see all my epics and also see the issues tied to them (not the substasks but the actual, TASKS -FEATURES - BUGS etc…) in a quick drop downView that makes for managing/visualizing the roadmap easy. The roadmap for mobile is lovely. But I just want to be able to see those items as well. It would make it a lot more useful and would definitely boost my confidence in using it. Thank you so much!! Developer Response Hi @agent619 - thank you for the detailed feedback and review. If I understand you correctly you want to see the epics in a single list with a dropdown to show you the tasks in the epic? If so maybe the list view on the roadmap tab will provide the info you are after? If this doesn't help, please send me an email so I can follow up on the feature request. Cheers,Jack Please add This feature to roadmap 04/30/2023 Agent619 Hi and thanks for the great app. I would really love to make Jira mobile a huge part of my planning process. It’s great for quick touch ups and reference glances or just knocking things out. There’s just a small thing that I want a little more on the roadmap.I want to be able to see the linked items per epic. When I’m on desktop, I can see all my epics and also see the issues tied to them (not the substasks but the actual, TASKS -FEATURES - BUGS etc…) in a quick drop downView that makes for managing/visualizing the roadmap easy. The roadmap for mobile is lovely. But I just want to be able to see those items as well. It would make it a lot more useful and would definitely boost my confidence in using it. Thank you so much!! Developer Response 05/16/2023 Hi @agent619 - thank you for the detailed feedback and review. If I understand you correctly you want to see the epics in a single list with a dropdown to show you the tasks in the epic? If so maybe the list view on the roadmap tab will provide the info you are after? If this doesn't help, please send me an email so I can follow up on the feature request. Cheers,Jack The Jira app is awesome compared to the desktop site 07/16/2020 JollyJoseph I wish the desktop website was half as good as the mobile app. For my office we are moving away from Jira as the web site has issues that we are not able to tolerate any longer. When I open My Open Issues, it presents the list of items in a column on the left l, but always brings up a random closed item on the right. Also, many times when I scroll down on the peg the top panel vanishes and the only way to see it again is to refresh the entire page. I have been using the mobile app instead as it’s so superior to the large landscape web site. Great job on the app. I really like its auto refresh features! The Jira app is awesome compared to the desktop site 07/16/2020 JollyJoseph I wish the desktop website was half as good as the mobile app. For my office we are moving away from Jira as the web site has issues that we are not able to tolerate any longer. When I open My Open Issues, it presents the list of items in a column on the left l, but always brings up a random closed item on the right. Also, many times when I scroll down on the peg the top panel vanishes and the only way to see it again is to refresh the entire page. I have been using the mobile app instead as it’s so superior to the large landscape web site. Great job on the app. I really like its auto refresh features! Can’t save an epic on current version of app on iPhone or iPad 09/11/2021 Haparose If I select or update an epic on a task, then leave the screen, it does not retain the value and reverts back to whatever it was before. It works fine on desktop but has never worked on my phone in the 6 months I’ve been using it. I have an old iPad mini 2 and it works fine there but the device is so old that it won’t let me update to the current version of Jira. I just upgraded to an iPad Pro with the latest version and it has the same problem my iPhone 11 does. Please fix this!!! It’s a huge problem for me that I can only update epics from desktop because I need to make updates from wherever I am. I am a Business Analyst III, so testing software is a huge part of my job and I’ve tried different things to get it to work but can’t find a workaround except to use a PC to make the change. I’m fairly certain this is a bug and I’m really surprised it’s gone unnoticed for this long. Please fix this!!! Developer Response Hi, sorry to hear about this persisting bug. We can't seem to reproduce this on our side, but would like to investigate it further. Can you please send us an email to jira-cloud-native@atlassian.com with more details on the issue? Perhaps a video showing the bug. And if you can reproduce this bug on your other Jira projects as well. Thank you! Can’t save an epic on current version of app on iPhone or iPad 09/11/2021 Haparose If I select or update an epic on a task, then leave the screen, it does not retain the value and reverts back to whatever it was before. It works fine on desktop but has never worked on my phone in the 6 months I’ve been using it. I have an old iPad mini 2 and it works fine there but the device is so old that it won’t let me update to the current version of Jira. I just upgraded to an iPad Pro with the latest version and it has the same problem my iPhone 11 does. Please fix this!!! It’s a huge problem for me that I can only update epics from desktop because I need to make updates from wherever I am. I am a Business Analyst III, so testing software is a huge part of my job and I’ve tried different things to get it to work but can’t find a workaround except to use a PC to make the change. I’m fairly certain this is a bug and I’m really surprised it’s gone unnoticed for this long. Please fix this!!! Developer Response 09/13/2021 Hi, sorry to hear about this persisting bug. We can't seem to reproduce this on our side, but would like to investigate it further. Can you please send us an email to jira-cloud-native@atlassian.com with more details on the issue? Perhaps a video showing the bug. And if you can reproduce this bug on your other Jira projects as well. Thank you! I have to consciously avoid using this app 08/07/2023 Ryan-in-Miami This app is still useless. I have to remember to avoid using it. Today, I made the mistake of opening an Epic in this app. After working with the problem for a while, I needed to create a new issue in that Epic. Ooops! That’s one of the things that Atlassian thinks is not important, so that was impossible. I had to kill the app, open a web browser, log into Jira, find the same epic by searching, and then create the issue. What a waste of time. What is the point of this app? Why does it exist? I keep forgetting that it’s nothing but a roadblock and I keep accidentally using it. I always regret it.2023 Update: It’s been YEARS since I wrote that review and there is STILL no way to create a new issue in an Epic in this iOS app. Why do people use this app? I’m deleting it yet again, and making a mental note to remind myself not to fall for Atlassian pushing it on me again.Atlassian, how does it make sense to you to offer such wildly, confusingly different interfaces through different channels? How does it make sense to you to simply not implement mission-critical functionality in the iOS app? Am I using Epics wrong by adding sub-issues or something?!? I wonder at least once a week why we still use Jira when it’s never going to get any better.[DELETING THIS ROADBLOCK OF AN APP YET AGAIN NOW…] Developer Response Hi Ryan, we've been listening and I wanted to let you know that we've just added iPad support. We hope you like it! I have to consciously avoid using this app 08/07/2023 Ryan-in-Miami This app is still useless. I have to remember to avoid using it. Today, I made the mistake of opening an Epic in this app. After working with the problem for a while, I needed to create a new issue in that Epic. Ooops! That’s one of the things that Atlassian thinks is not important, so that was impossible. I had to kill the app, open a web browser, log into Jira, find the same epic by searching, and then create the issue. What a waste of time. What is the point of this app? Why does it exist? I keep forgetting that it’s nothing but a roadblock and I keep accidentally using it. I always regret it.2023 Update: It’s been YEARS since I wrote that review and there is STILL no way to create a new issue in an Epic in this iOS app. Why do people use this app? I’m deleting it yet again, and making a mental note to remind myself not to fall for Atlassian pushing it on me again.Atlassian, how does it make sense to you to offer such wildly, confusingly different interfaces through different channels? How does it make sense to you to simply not implement mission-critical functionality in the iOS app? Am I using Epics wrong by adding sub-issues or something?!? I wonder at least once a week why we still use Jira when it’s never going to get any better.[DELETING THIS ROADBLOCK OF AN APP YET AGAIN NOW…] Developer Response 04/28/2017 Hi Ryan, we've been listening and I wanted to let you know that we've just added iPad support. We hope you like it! What’s New Version History Bugs were annihilated, and improvements were made. 245.2.0 12/14/2025 Bugs were annihilated, and improvements were made. 245.1.0 12/10/2025 Bugs were annihilated, and improvements were made. 244.2.0 12/01/2025 Bugs were annihilated, and improvements were made. 244.1.0 11/28/2025 Bugs were annihilated, and improvements were made. 244.0.0 11/25/2025 Bugs were annihilated, and improvements were made. 243.2.0 11/19/2025 Bugs were annihilated, and improvements were made. 243.1.0 11/11/2025 Bugs were annihilated, and improvements were made. 242.0.0 10/28/2025 Bugs were annihilated, and improvements were made. 241.1.0 10/20/2025 Bugs were annihilated, and improvements were made. 241.0.0 10/13/2025 Bugs were annihilated, and improvements were made. 240.2.0 10/01/2025 Bugs were annihilated, and improvements were made. 239.1.0 09/17/2025 Bugs were annihilated, and improvements were made. 238.1.0 09/12/2025 Bugs were annihilated, and improvements were made. 238.0.0 09/01/2025 Bugs were annihilated, and improvements were made. 237.1.0 08/18/2025 * Fixed issue with presenting keyboard on login 236.2.0 08/10/2025 * Squashed bugs 236.1.0 08/06/2025 Bugs were annihilated, and improvements were made. 235.0.0 07/21/2025 Bugs were annihilated, and improvements were made. 234.0.1 07/15/2025 Bugs were annihilated, and improvements were made. 234.0.0 07/07/2025 Bugs were annihilated, and improvements were made. 233.3.0 07/02/2025 Bugs were annihilated, and improvements were made. 233.2.0 06/27/2025 Bugs were annihilated, and improvements were made. 233.1.0 06/25/2025 Bugs were annihilated, and improvements were made. 232.0.0 06/10/2025 Bugs were annihilated, and improvements were made. 231.0.0 05/27/2025 Bugs were annihilated, and improvements were made. more Version 245.2.0 12/14/2025 App Privacy App Privacy The developer, Atlassian , indicated that the app’s privacy practices may include handling of data as described below. This information has not been verified by Apple. For more information, see the developer’s privacy policy . To help you better understand the developer’s responses, see Privacy Definitions and Examples . Privacy practices may vary, for example, based on the features you use or your age. Learn More Data Linked to You The following data, which may be collected and linked to your identity, may be used for the following purposes: Analytics Identifiers User ID App Functionality Contact Info Email Address Name Identifiers User ID Data Not Linked to You The following data, which may be collected but is not linked to your identity, may be used for the following purposes: Analytics Location Coarse Location Identifiers Device ID Diagnostics Crash Data Performance Data Other Diagnostic Data Other Data Other Data Types The developer, Atlassian , indicated that the app’s privacy practices may include handling of data as described below. For more information, see the developer’s privacy policy . Data Linked to You The following data may be collected and linked to your identity: Contact Info Identifiers Data Not Linked to You The following data may be collected but it is not linked to your identity: Location Identifiers Diagnostics Other Data Privacy practices may vary, for example, based on the features you use or your age. Learn More Accessibility The developer has not yet indicated which accessibility features this app supports. Learn More Information Seller Atlassian Pty Ltd Size 407.9 MB Category Productivity Compatibility Requires iOS 17.0 or later. iPhone Requires iOS 17.0 or later. iPad Requires iPadOS 17.0 or later. Languages English and 26 more English, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Icelandic, Italian, Japanese, Korean, Norwegian Bokmål, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Slovak, Spanish, Swedish, Thai, Traditional Chinese, Turkish, Ukrainian, Vietnamese Age Rating 4+ 4+ Learn More Copyright © 2025 Atlassian Pty Ltd Developer Website Privacy Policy License Agreement More by Atlassian Confluence Cloud Collaborate on the go View Confluence Data Center Work together from anywhere View Jira Data Center Track tasks, projects & work View Atlassian Rovo AI built for teamwork View You Might Also Like ClickUp: Tasks, Chat, Docs, AI #1 AI Workspace & Agents View Microsoft Planner Productivity View Miro: your visual workspace Build the next big thing View Airtable Productivity View Microsoft Loop Think, plan & create together View Glean Work Search that works View 1Password: Password Manager Save & share passwords safely View Craft: Docs, Notes, Tasks & AI AI-powered docs & second brain View Bitwarden Password Manager Secure your digital life View MaintainX Work Orders Maintenance Management CMMS View United States Español (México) العربية Русский 简体中文 Français (France) 한국어 Português (Brazil) Tiếng Việt 繁體中文 (台灣) Select a country or region Africa, Middle East, and India See All Algeria Angola Armenia Azerbaijan Bahrain Benin Botswana Brunei Darussalam Burkina Faso Cameroun Cape Verde Chad Côte d’Ivoire Congo, The Democratic Republic Of The Egypt Eswatini Gabon Gambia Ghana Guinea-Bissau India Iraq Israel Jordan Kenya Kuwait Lebanon Liberia Libya Madagascar Malawi Mali Mauritania Mauritius Morocco Mozambique Namibia Niger (English) Nigeria Oman Qatar Congo, Republic of Rwanda São Tomé and Príncipe Saudi Arabia Senegal Seychelles Sierra Leone South Africa Sri Lanka Tajikistan Tanzania, United Republic Of Tunisia Turkmenistan United Arab Emirates Uganda Yemen Zambia Zimbabwe Asia Pacific See All Afghanistan Australia Bhutan Cambodia 中国大陆 Fiji 香港 Indonesia (English) 日本 Kazakhstan 대한민국 Kyrgyzstan Lao People's Democratic Republic 澳門 Malaysia (English) Maldives Micronesia, Federated States of Mongolia Myanmar Nauru Nepal New Zealand Pakistan Palau Papua New Guinea Philippines Singapore Solomon Islands 台灣 Thailand Tonga Turkmenistan Uzbekistan Vanuatu Vietnam Europe See All Albania Armenia Österreich Belarus Belgium Bosnia and Herzegovina Bulgaria Croatia Cyprus Czechia Denmark Estonia Finland France (Français) Georgia Deutschland Greece Hungary Iceland Ireland Italia Kosovo Latvia Lithuania Luxembourg (English) Malta Moldova, Republic Of Montenegro Nederland North Macedonia Norway Poland Portugal (Português) Romania Россия Serbia Slovakia Slovenia España Sverige Schweiz Türkiye (English) Ukraine United Kingdom Latin America and the Caribbean See All Anguilla Antigua and Barbuda Argentina (Español) Bahamas Barbados Belize Bermuda Bolivia (Español) Brasil Virgin Islands, British Cayman Islands Chile (Español) Colombia (Español) Costa Rica (Español) Dominica República Dominicana Ecuador (Español) El Salvador (Español) Grenada Guatemala (Español) Guyana Honduras (Español) Jamaica México Montserrat Nicaragua (Español) Panamá Paraguay (Español) Perú St. Kitts and Nevis Saint Lucia St. Vincent and The Grenadines Suriname Trinidad and Tobago Turks and Caicos Uruguay (English) Venezuela (Español) The United States and Canada See All Canada (English) Canada (Français) United States Estados Unidos (Español México) الولايات المتحدة США 美国 (简体中文) États-Unis (Français France) 미국 Estados Unidos (Português Brasil) Hoa Kỳ 美國 (繁體中文台灣) Copyright © 2026 Apple Inc. All rights reserved. Internet Service Terms App Store & Privacy Cookie Warning Support | 2026-01-13T09:29:44 |
https://git-scm.com/book/de/v2/Git-Grundlagen-Zusammenfassung | Git - Zusammenfassung About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 2.8 Git Grundlagen - Zusammenfassung Zusammenfassung Du solltest jetzt in der Lage sein, die wichtigsten Git-Befehle einsetzen zu können. Folgendes sollte Dir jetzt gelingen: Erzeugen oder Klonen eines Repositorys, Änderungen vornehmen und zur Staging-Area hinzufügen, Commits anlegen und die Historie aller Commits in einem Repository durchsuchen. Als nächstes werden wir uns mit der „Killer-Funktion“ von Git befassen: dem Branching-Modell. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Resumen | Git - Resumen About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.8 Fundamentos de Git - Resumen Resumen En este momento puedes hacer todas las operaciones básicas de Git a nivel local: Crear o clonar un repositorio, hacer cambios, preparar y confirmar esos cambios y ver la historia de los cambios en el repositorio. A continuación cubriremos la mejor característica de Git: Su modelo de ramas. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/zh/software/jira/templates/sales | 销售模板 | Jira 模板库 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Jira 模板 Open and close the navigation menu 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 免费获取 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 销售模板 Drive your deals to success with Jira. With pre-built, customizable templates for sales teams, it’s easy to get started. 项目管理 管理用于完成业务项目的活动。 销售渠道 从新的潜在客户到交易完成，全程跟踪潜在客户。 销售服务管理 管理、跟踪和报告您的所有销售请求。 潜在客户跟踪 跟踪销售线索，从销售机会到销售结束。 销售资源 Jira for sales teams Manage your pipeline from start to close. Learn more about how Jira helps streamline your work. 了解更多 通过自动化机制来完成项目 专注于重要事务，剩下的事情交给自动化机制完成。创建团队的自定义规则，或者通过我们的预设自动化功能快速开始。 探索自动化 连接您最喜欢的工具 利用 500 多种集成实现无缝工作，借助 3,000 多个其他扩展来打造团队的完美流程。 探索应用市场 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://www.atlassian.com/zh/software/jira/templates/operations | 运营模板 | Jira 模板库 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Jira 模板 Open and close the navigation menu 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 免费获取 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 运营模板 轻松简化流程。借助为运营团队预先构建的可自定义模板，轻松开始工作。 项目管理 管理用于完成业务项目的活动。 活动规划 计划下次活动并简化所有细节。 采购 跟踪从请求到接收的所有采购。 流程控制 消除流程中的重复内容。 政策管理 跟踪管理政策和程序中涉及的活动部分。 常规服务管理 对所有业务团队的请求进行收集、优先级排序和管理。 设施服务管理 管理针对维护、移动和活动规划的请求。 运营资源 适用于运营团队的 Jira 创建与众不同的流程。详细了解 Jira Work Management 如何帮您简化工作。 了解更多 通过自动化机制来完成项目 专注于重要事务，剩下的事情交给自动化机制完成。创建团队的自定义规则，或者通过我们的预设自动化功能快速开始。 探索自动化 连接您最喜欢的工具 利用 500 多种集成实现无缝工作，借助 3,000 多个其他扩展来打造团队的完美流程。 探索应用市场 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://git-scm.com/book/pt-br/v2/Fundamentos-de-Git-Sum%c3%a1rio | Git - Sumário About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.8 Fundamentos de Git - Sumário Sumário Nesse ponto, você já pode executar todas as operações locais básicas do Git - como criar ou clonar um repositório, fazer alterações, usar stage e commit para essas alterações e visualizar o histórico de todas as alterações pelas quais o repositório passou. A seguir, abordaremos o recurso matador do Git: seu modelo de ramificação ( branch ). prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%9f%d0%b0%d0%ba%d0%b5%d1%82%d0%b8-%d0%b2-Git-Bundling | Git - Пакети в Git (Bundling) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.12 Git инструменти - Пакети в Git (Bundling) Пакети в Git (Bundling) Вече разгледахме стандартните начини за трансфер на Git данни по мрежата (HTTP, SSH и т.н.), но има и още един начин да правим това, който е не толкова често използван, а може да бъде полезен. Git може да “пакетира” своите данни в единичен файл. Това може да е ценно в различни ситуации. Може би мрежата ви е повредена, а искате да изпратите промените си до колегите. Може да работите някъде далеч офлайн и да нямате достъп до локалната офис мрежа. Дори може мрежовата ви карта да е повредена. Може да нямате достъп до споделен сървър за момента, искате да изпратите по имейла промени на някого, но не желаете да изпращате много къмити през format-patch . Тук може да помогне командата git bundle . Тази команда ще пакетира всичко, което нормално би изпратено по мрежата с git push в единичен бинарен файл, който може да се изпрати по имейл или чрез флашка и след това да се разпакетира в друго хранилище. Нека видим прост пример. Да кажем, че имате хранилище с два къмита: $ git log commit 9a466c572fe88b195efd356c3f2bbeccdb504102 Author: Scott Chacon <schacon@gmail.com> Date: Wed Mar 10 07:34:10 2010 -0800 Second commit commit b1ec3248f39900d2a406049d762aa68e9641be25 Author: Scott Chacon <schacon@gmail.com> Date: Wed Mar 10 07:34:01 2010 -0800 First commit Ако искате да го изпратите към някой друг, но нямате достъп до хранилище, в което да публикувате или пък просто не искате да правите такова, можете да пакетирате хранилището с git bundle create . $ git bundle create repo.bundle HEAD master Counting objects: 6, done. Delta compression using up to 2 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (6/6), 441 bytes, done. Total 6 (delta 0), reused 0 (delta 0) Сега ще имате локален файл с име repo.bundle , който съдържа всичко необходимо за пресъздаване на master клона на хранилището ви някъде другаде. С командата bundle трябва да посочите всяка референция или специфичен набор от къмити, които искате да бъдат включени. Ако желаете нещата да бъдат клонирани на друго място, трябва да посочите HEAD като референция както направихме току що. Можете да изпратите файла по имейл или да го копирате на флашка за когото е нужно. Ако сте от другата страна и имате вече такъв файл, ето как да го използвате. Клонираме от бинарния файл в директория също както от URL. $ git clone repo.bundle repo Cloning into 'repo'... ... $ cd repo $ git log --oneline 9a466c5 Second commit b1ec324 First commit Ако HEAD не е бил включен в референциите, ще трябва също да укажем -b master или съответното име на клон, така че Git да знае кой клон да извлече в работната директория. Нека сега предположим, че сме направили промени в три къмита и искаме да ги изпратим обратно в пакет на USB флашка или по имейла. $ git log --oneline 71b84da Last commit - second repo c99cf5b Fourth commit - second repo 7011d3d Third commit - second repo 9a466c5 Second commit b1ec324 First commit Първо, трябва да определим обхвата от къмити, които да включим в пакета. За разлика от случая с мрежовите протоколи, които определят това вместо нас, ще трябва да го подадем ръчно. Можете да направите същото нещо като в началото и да пакетирате цялото хранилище, това ще работи, но по-елегантно е да пакетирате само разликите, тоест само трите къмита направени локално. За да направите това, ще трябва да калкулирате разликите. Както описахме в Обхвати от къмити , можете да указвате обхват от къмити по няколко начина. За да вземем само локалните три къмита, които липсват в оригинално клонирания клон, бихме могли да използваме нещо като origin/master..master или master ^origin/master . Можем да тестваме това с командата log . $ git log --oneline master ^origin/master 71b84da Last commit - second repo c99cf5b Fourth commit - second repo 7011d3d Third commit - second repo След като сега имаме списъка къмити, нека ги обединим в пакет. Правим това със същата git bundle create команда, предоставяйки ѝ като параметри името на пакетния файл и обхвата от къмити. $ git bundle create commits.bundle master ^9a466c5 Counting objects: 11, done. Delta compression using up to 2 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (9/9), 775 bytes, done. Total 9 (delta 0), reused 0 (delta 0) Сега имаме файла commits.bundle в директорията ни. Ако го изпратим на наш колега, той/тя може да го импортира в оригиналното хранилище дори ако там междувременно е свършена и друга работа. Другата страна има възможност да инспектира съдържанието на пакета преди импорта. Първата команда е bundle verify и тя ще провери, че файлът в действителност е валиден Git пакет и че налице са всички необходими родителски обекти за коректното му импортиране. $ git bundle verify ../commits.bundle The bundle contains 1 ref 71b84daaf49abed142a373b6e5c59a22dc6560dc refs/heads/master The bundle requires these 1 ref 9a466c572fe88b195efd356c3f2bbeccdb504102 second commit ../commits.bundle is okay Ако човекът направил пакета беше го сглобил само от двата последни къмита вместо от всичките три, оригиналното хранилище няма да може да ги внедри поради липса на пълна история. В такъв случай изходът от командата verify би изглеждал така: $ git bundle verify ../commits-bad.bundle error: Repository lacks these prerequisite commits: error: 7011d3d8fc200abe0ad561c011c3852a4b7bbe95 Third commit - second repo В нашия случай пакетът си е валиден, така че можем да извлечем къмитите от него. Ако искате да видите какви клонове съдържа пакета, също можете да го направите: $ git bundle list-heads ../commits.bundle 71b84daaf49abed142a373b6e5c59a22dc6560dc refs/heads/master Подкомандата verify може също да ви даде тази информация. Целта е да се види какво може да бъде слято, така че можем да използваме fetch или pull за да импортираме къмити от този пакет. Тук ще издърпаме master клона от пакета в клон наречен other-master в нашето хранилище: $ git fetch ../commits.bundle master:other-master From ../commits.bundle * [new branch] master -> other-master Сега можем да видим, че имаме импортираните къмити в клона other-master както и междувременно направените такива в нашия собствен master клон. $ git log --oneline --decorate --graph --all * 8255d41 (HEAD, master) Third commit - first repo | * 71b84da (other-master) Last commit - second repo | * c99cf5b Fourth commit - second repo | * 7011d3d Third commit - second repo |/ * 9a466c5 Second commit * b1ec324 First commit И така, видяхме как git bundle може да е ценен помощник за споделяне на работа, когато не разполагаме с необходимата мрежова свързаност. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/recording/automating-manual-tests.html#zephyr-essential | Automating Manual Tests | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Recording Automating Manual Tests Automating Manual Tests Using our free Chrome extension , you can run your manual test cases as automated tests in Reflect directly from your existing test case management tool. Running tests Reflect 's free Chrome extension lets you run your manual test cases as automated Reflect tests. Tests can be run from our extension without even needing to have an existing Reflect account. Note that in order to view the results of a test run (including a video recording of the run, pass/fail details, and console/network logs), you’ll be prompted to create a free Reflect account if don’t already have one. Reflect leverages Generative AI to interpret and execute a manual test script as an automated test. Each step within your manual test effectively becomes an AI “prompt” that serves as the input to our AI engine. At runtime, the Reflect AI engine takes these inputs and analyzes the current state of the application to determine what actions and/or assertions need to be performed in order to fulfill each test step. Our Chrome extension displays test results in realtime, and provides the ability to watch tests run live within Reflect with a single click. You can also see the history of test runs for a given test, and click to view the results of any test run. If you’re in the middle of a regression test pass (sometimes called a Test Run or Test Cycle depending on the tool you use), then the test runs you create will be named after the Test Run / Test Cycle. This makes it easier to understand the context of historical test runs when you view them later. Updating tests When running tests via our Chrome extension, the source-of-truth of the test becomes the test steps defined within your test case management tool. Any updates made to your test case will be captured and synced to Reflect the next time you run your test case via our Chrome extension. Linking to an existing Reflect account If you are already a Reflect customer, you can link the Chrome extension to your Reflect account via the following steps: Within the Reflect web app, navigate to the Settings section. Under Account Information, find the section entitled ‘ Reflect Extension’. If an Extension API Key does not already exist, click the ‘Generate Extension API Key’ button to create one. Copy the Extension API Key to your clipboard. Next, open the Reflect Chrome extension by clicking the Reflect icon in the Chrome toolbar. Click the gear icon in the top-right of the sidepanel that is displayed. Paste the Extension API Key value into the input field, and click ‘Update Settings’. Your Chrome extension is now linked to your Reflect account. Any tests executed from the Chrome extension will now appear in your existing Reflect account. Supported Integrations The following test case management tools are supported by our Chrome extension: Test Rail Within TestRail, you can execute test cases automatically from both the Test Case view, as well as within the context of a Test Run. TEST CASE Go to the Test Cases section and click on a test case. Any test case that contains a ‘Steps’ section that has individual test steps (such as when using the ‘Test Case (Steps)’ template) can be executed by Reflect . To run a test case automatically, click the ‘Run as Automated Test’ button that appears in the sidebar, or click on the Reflect extension icon within the Chrome toolbar. The sidepanel will open and provide options for executing the test case. TEST RUN Test Cases can also be executed automatically within the context of a Test Run. To run a test case automatically, navigate to your Test Run and click the ‘Activity’ link in the sidebar to view the list of test cases in this run. Click the desired test case within the Activity section. To run the test case from this view, either click the ‘Run as Automated Test’ button, or click on the Reflect extension icon within the Chrome toolbar. The sidepanel will provide options for executing the test case. Xray To run an Xray test, simply navigate to any Jira issue that is an Xray test and either click the ‘Run as Automated Test’ button that appears above the list of test steps, or click on the Reflect extension icon within the Chrome toolbar when viewing the Xray test. Please note that for an Xray test to be executable within Reflect , it must contain at least one test step. If you’re using Xray’s default settings, the test will need to have a Test Type of ‘Manual’ to allow individual test steps to be defined. Zephyr Within Zephyr , you can execute test cases from either the Test Case view, or within the Test Cycle player. TEST CASE Any Test Case that has a ‘Type’ of ‘Step by Step’ can be run automatically using the Reflect Chrome extension. To run a test case automatically, first click on the ‘Test Script’ tab when viewing a test case. A ‘Run as Automated Test’ button will appear within the Test Script section. Options for running the test case will appear in the sidepanel after clicking the ‘Run as Automated Test’ button, or after clicking on the Reflect extension icon within the Chrome toolbar. TEST CYCLE PLAYER Test Cases can also be executed automatically within the context of a Test Cycle. To run a test case automatically, first navigate to your desired Test Cycle (e.g. by clicking Zephyr on the sidebar, selecting the Test Cycles tab, and clicking a Test Cycle from the list). Each Test Case within the cycle can be executed automatically by selecting the Test Case in the left sidebar and subsequently clicking on either the ‘Run as Automated Test’ button that appears, or by clicking on the Reflect extension icon within the Chrome toolbar. Zephyr Essential Tests can be executed when viewing an individual Test, or when viewing a Cycle Summary. TEST CASE First, navigate to the Jira issue that represents the Zephyr Essential Test that you wish to run. Within the Test Details section, a ‘Run as Automated Test’ button will appear. Clicking this button or clicking the Reflect extension icon will reveal a sidepanel that displays options for running the Test automatically in Reflect . CYCLE SUMMARY Tests can also be executed automatically within the context of a Cycle. First, navigate to the Cycle Summary by clicking Zephyr Essential in the left sidebar and clicking the Cycle Summary link. Next, select your desired Cycle and enable the ‘Detail’ view if it is not already active. A ‘Run as Automated Test’ button will appear within the Cycle Summary view. Clicking this button or clicking the Reflect extension icon will reveal a sidepanel that displays options for running the Test automatically in Reflect . In this section : Automating Manual Tests Running tests Updating tests Linking to an existing Reflect account Supported Integrations Test Rail Xray Zephyr Zephyr Essential Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://www.linkedin.com/products/hubbedin-ai-resume-builder/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click#main-content | AI Resume Builder | LinkedIn Skip to main content LinkedIn HubbedIn in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in AI Resume Builder AI-Powered Coaching Software by HubbedIn See who's skilled in this Add as skill Try now Report this product About HubbedIn's Resume Builder is an AI-powered tool designed to simplify the resume creation process. It assists job seekers in crafting professional resumes effortlessly, offering personalized suggestions and rephrasing sentences to meet specific job requirements. Our AI tool aims to elevate job seekers' applications by ensuring your resumes stand out and accurately reflect your achievements and skills. Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software CoachHub - The digital coaching platform CoachHub - The digital coaching platform AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Yoodli AI Roleplays Yoodli AI Roleplays AI-Powered Coaching Software Sign in to see more Show more Show less HubbedIn products AI Video Interviewer AI Video Interviewer Video Interview Software Find a Hiring Manager Find a Hiring Manager AI-Powered Coaching Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:44 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fhubbedin-find-a-hiring-manager&fromSignIn=true&trk=products_details_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:44 |
https://git-scm.com/book/fa/v2/%d9%85%d9%82%d8%af%d9%85%d8%a7%d8%aa-%da%af%db%8c%d8%aa-git-basics-chapter-%d8%ae%d9%84%d8%a7%d8%b5%d9%87-summary | Git - خلاصه (summary) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 2.8 مقدمات گیت (git basics chapter) - خلاصه (summary) خلاصه (summary) تا به اینجا، تمام عملیاتهای پایه و محلی گیت را میتوانید انجام دهید — ساختن یا کلون کردن یک مخزن، اعمال تغییرات، استیج و کامیت کردن آن تغییرات و مشاهده تاریخچه تمام تغییرات اعمال شده روی مخزن. پس از این به خفنترین ویژگی گیت میپردازیم: مدل شاخهسازی آن. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.digitalcameraworld.com/uk/tech/printers#main | Printer Reviews, News and Buying Guides | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY UK Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From £9.99 Subscribe now Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . Tech Printers Printers Latest about Printers Instax is about to get a lot better at printing text on instant film, if this new premium mobile printer is any indication By Hillary K. Grigonis published 7 January 26 INSTAX Fujifilm's Instax Mini Link+ is a portable photo printer made to also print text and graphics, but it has only been announced in Japan INSTAX "Until a photo is printed, it’s just a jumble of binary code buried on a hard drive." It's time to be your own biggest fan and start printing your favorites! By Matthew Richards published 4 January 26 Features Show your work a little love this year and invest in a printer to turn your house into your very own art gallery Features Hurry! This Fujifilm Instax Square portable printer has been slashed to just £74.25 By Chris George published 23 December 25 Deals Save nearly $90 in this one-day mega deal from Adorama Deals Epson EcoTank ET-2980 / ET-2950 review: a bottle-fed printer with a reasonable purchase price and cheap running costs By Matthew Richards published 3 December 25 Review The Epson EcoTank ET-2950 / ET-2980 home office multi-function printer won’t break the bank to buy and its running costs could save a small fortune in the long run Review Epson EcoTank ET-4950 review: a money-stretching, all-in-one, bottle-fed printer, complete with fax By Matthew Richards published 3 December 25 Review The Epson EcoTank ET-4950 aims to minimize running costs while maximizing usefulness in the home office, with truly all-in-one aspirations Review Printers are frustrating. This is the photo printer that I finally fell in love with as a pro photographer – and the price has never been lower By Hillary K. Grigonis last updated 1 December 25 OPINION The Epson EcoTank ET-8550 has dropped to its lowest price ever during Cyber Monday OPINION Go big or go home! Save £250 on Epson large-format photo printer in early Black Friday deal By Sebastian Oakley published 21 November 25 Epson Surecolor SC-P700 and P900 A3 & A2 printers get big discounts at Wex Printers Mini photo printers are one of the trendiest gifts of the year, according to Google. As a photographer, I think these are the best deals on top-ranked options By Hillary K. Grigonis published 19 November 25 TRENDS Google says searches for photo printers are up by 65 percent this year, making them one of the trendiest gifts TRENDS The best portable printers: make real prints of your shots for sharing while you’re in the moment By James Artaius last updated 13 November 25 BUYING GUIDE With one of the best portable printers, you can make prints anywhere and everywhere, to share with friends and family. BUYING GUIDE The best photo printer: here's my pick of the top printers for creating A4, A3 and A2 photos By Matthew Richards last updated 7 November 25 Updated The best photo printers empower you to create spectacular color and mono photo prints at home. Here's my pick of the bunch… Updated 1 2 3 4 5 6 7 8 9 Archives Get the Digital Camera World Newsletter The best camera deals, reviews, product advice, and unmissable photography news, direct to your inbox! Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. LATEST ARTICLES 1 I took photos of 36 electric boxes in Buenos Aires and made some decent dough from them. Odd subjects often pay better than postcard views 2 100 winning portraits turn Britain's streets into a nationwide photography exhibition 3 Super-popular mirrorless camera drops to its lowest price ever! 4 Rugged phones completely changed my life in 2025 – here's why these big beasts have become my most trusted travelling companions 5 DJI Osmo Mobile 8 review: A pro-grade phone gimbal that keeps up with ambitious creators without breaking the bank Digital Camera World is part of Future plc, an international media group and leading digital publisher. Visit our corporate site . Add as a preferred source on Google Terms and conditions Contact Future's experts Privacy policy Cookies policy Advertise with us About us Accessibility Statement Careers © Future Publishing Limited Quay House, The Ambury, Bath BA1 1UA. All rights reserved. England and Wales company registration number 2008885. Close Please login or signup to comment Please wait... Login Sign Up | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%94%d0%b5%d0%b1%d1%8a%d0%b3%d0%b2%d0%b0%d0%bd%d0%b5-%d1%81-Git | Git - Дебъгване с Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.10 Git инструменти - Дебъгване с Git Дебъгване с Git В допълнение на основната си задача за контрол на версиите, Git също така осигурява някои команди, които могат да ви помогнат при търсене на грешки в сорс кода. Понеже Git е проектиран да обслужва всякакъв вид съдържание, тези инструменти са доста общи, не навлизат в дълбочина, но въпреки това често могат да бъдат полезни. Анотации на файлове Ако проследявате дадена грешка в кода си и искате да разберете кога и как е възникнала, файловите анотации често са най-добрия начин да направите това. Те показват кой е последния къмит модифицирал всеки един ред от произволен файл. Така че, ако срещнете метод с бъгав код в него, можете да анотирате файла с командата git blame за да установите кой къмит е въвел в кода специфичния ред или редове от код. Следващият пример използва git blame за да установи кои къмити и разработчици са отговорни за редовете код от един Makefile файл в проекта на Linux ядрото и освен това използва флага L за да ограничи изхода до редовете между 69 и 82: $ git blame -L 69,82 Makefile b8b0618cf6fab (Cheng Renquan 2009-05-26 16:03:07 +0800 69) ifeq ("$(origin V)", "command line") b8b0618cf6fab (Cheng Renquan 2009-05-26 16:03:07 +0800 70) KBUILD_VERBOSE = $(V) ^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 71) endif ^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 72) ifndef KBUILD_VERBOSE ^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 73) KBUILD_VERBOSE = 0 ^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 74) endif ^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 75) 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 76) ifeq ($(KBUILD_VERBOSE),1) 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 77) quiet = 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 78) Q = 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 79) else 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 80) quiet=quiet_ 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 81) Q = @ 066b7ed955808 (Michal Marek 2014-07-04 14:29:30 +0200 82) endif Първото поле в ляво на таблицата е част от SHA-1 хеша на къмита, който последно е модифицирал съответния ред. Следващите две колони се извличат от самия къмит — името на автора му и датата на къмита. В следващите колони идват номера и съдържанието на реда от файла. Отбележете също и редовете започващи с ^1da177e4c3f4 , при тях префикса ^ обозначава, че те са били създадени с първия къмит на хранилището и след това не са променяни нито веднъж. Този вид обозначение причинява малко смут, защото досега видяхме поне три различни начина, при които Git използва този символ за да модифицира SHA-1 хеш стойностите, но в този конкретен случай това е неговото значение. Друга хубава черта на Git е, че не проследява изрично преименуванията на файловете. Git записва snapshot-ите и след това се опитва да установи какво е било безусловно преименувано постфактум. Една от интересните особености на това е, че можете да правите запитвания и за премествания на код. С параметър -C към git blame Git анализира файла, който анотирате и се опитва да установи откъде са се появили дадени отрязъци от код, ако те са копирани от друго място. Например, да кажем че преработвате файл с име GITServerHandler.m в множество файлове, един от които се казва GITPackUpload.m . Изследвайки GITPackUpload.m с параметър -C , можете да видите къде първоначално са се намирали секции код от него: $ git blame -C -L 141,153 GITPackUpload.m f344f58d GITServerHandler.m (Scott 2009-01-04 141) f344f58d GITServerHandler.m (Scott 2009-01-04 142) - (void) gatherObjectShasFromC f344f58d GITServerHandler.m (Scott 2009-01-04 143) { 70befddd GITServerHandler.m (Scott 2009-03-22 144) //NSLog(@"GATHER COMMI ad11ac80 GITPackUpload.m (Scott 2009-03-24 145) ad11ac80 GITPackUpload.m (Scott 2009-03-24 146) NSString *parentSha; ad11ac80 GITPackUpload.m (Scott 2009-03-24 147) GITCommit *commit = [g ad11ac80 GITPackUpload.m (Scott 2009-03-24 148) ad11ac80 GITPackUpload.m (Scott 2009-03-24 149) //NSLog(@"GATHER COMMI ad11ac80 GITPackUpload.m (Scott 2009-03-24 150) 56ef2caf GITServerHandler.m (Scott 2009-01-05 151) if(commit) { 56ef2caf GITServerHandler.m (Scott 2009-01-05 152) [refDict setOb 56ef2caf GITServerHandler.m (Scott 2009-01-05 153) Това е наистина полезно. Нормално бихте получили като оригинален къмит този, при който сте вмъкнали съдържанието в новия файл, защото това е първия път, когато сте докоснали тези редове в този файл. Git обаче може да ви намери и оригиналния къмит, в който сте написали тези редове, дори те да са били в друг файл. Бинарно търсене Анотирането на файлове помага, когато знаете къде започва проблема. Ако обаче не знаете какво се е счупило и има дузина или стотици къмити от последния път, когато знаете че кодът е работил, вероятно ще прибегнете до помощта на git bisect . Командата bisect се използва за бинарно търсене в историята на къмитите за да ви помогне да идентифицирате даден проблем възможно най-бързо. Нека кажем, че сте публикували завършена версия на кода си и започвате да получавате новини за грешки, които не се наблюдават в работната версия и нямате идея защо кодът се държи така. Връщате се обратно в кода и се оказва, че всъщност можете да пресъздадете грешката, но все още не разбирате защо възниква. В такъв случай можете да bisect-нете (разполовите) кода за да потърсите причината (понятието идва от начина, по който Git третира и разцепва историята в процеса на търсене описан в примерите, които следват). Първо, изпълнявате git bisect start за да стартирате процеса и след това git bisect bad за да кажете на системата, че текущия къмит е проблематичен. След това, трябва да кажете на bisect кога е бил последния работещ статус на нещата изпълнявайки git bisect good <good_commit> : $ git bisect start $ git bisect bad $ git bisect good v1.0 Bisecting: 6 revisions left to test after this [ecb6e1bc347ccecc5f9350d878ce677feb13d3b2] Error handling on repo Git е установил около 12 къмита, които са се случили между този, който сте маркирали като последно работещ (v1.0) и текущата проблемна версия и е извлякъл за вас средния от тях. На този етап, можете да си пуснете тестовете, за да видите дали проблемът все още се появява в този извлечен къмит. Ако е така, то той е възникнал някъде преди средния къмит. Ако не е, значи възниква след него. Да кажем, че проблемът го няма на текущия къмит — вие уведомявате Git за това с git bisec good и продължавате да търсите: $ git bisect good Bisecting: 3 revisions left to test after this [b047b02ea83310a70fd603dc8cd7a6cd13d15c04] Secure this thing Сега сте на друг къмит, който е по средата между този който току що тествахте и проблематичния. Пускате тестовете отново и този път установявате, че грешката се появява и уведомявате Git с git bisect bad : $ git bisect bad Bisecting: 1 revisions left to test after this [f71ce38690acf49c1f3c9bea38e09d82a5ce6014] Drop exceptions table Този къмит е безпроблемен и сега Git има информацията, която му е нужна за да разбере къде се е появил проблема. Вие получавате SHA-1 хеша на първия проблемен къмит, заедно с малко данни за него и списък на модифицираните файлове така че да успеете да установите източника на грешката: $ git bisect good b047b02ea83310a70fd603dc8cd7a6cd13d15c04 is first bad commit commit b047b02ea83310a70fd603dc8cd7a6cd13d15c04 Author: PJ Hyett <pjhyett@example.com> Date: Tue Jan 27 14:48:32 2009 -0800 Secure this thing :040000 040000 40ee3e7821b895e52c1695092db9bdc4c61d1730 f24d3c6ebcfc639b1a3814550e62d60b8e68a8e4 M config Когато приключите, трябва да изпълните git bisect reset за да пренасочите HEAD към мястото, където сте били преди да стартирате процеса: $ git bisect reset Това е мощен инструмент, който за минути може да провери стотици къмити в процеса на търсене на грешка. В допълнение, ако имате скрипт, който завършва със статус exit 0, ако проектът работи коректно или с различен статус, ако това не е така, можете напълно да автоматизирате git bisect . Първо, вие отново указвате обхвата на bisect подавайки познатите добър и лош къмит. Можете да направите това изписвайки ги с bisect start командата, първо подавате лошия (HEAD) и след това последно познатия добър (v1.0): $ git bisect start HEAD v1.0 $ git bisect run test-error.sh Правейки това, Git автоматично ще изпълнява test-error.sh за всеки извлечен къмит докато намери първия проблематичен. Можете също да изпълнявате неща като make или make tests или каквото и да било друго средство, което използвате за автоматично тестване. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/%d0%9d%d0%b0%d1%87%d0%b0%d0%bb%d0%be-%d0%9f%d0%be%d0%bc%d0%be%d1%89%d0%bd%d0%b0-%d0%b8%d0%bd%d1%84%d0%be%d1%80%d0%bc%d0%b0%d1%86%d0%b8%d1%8f-%d0%b2-Git | Git - Помощна информация в Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 1.7 Начало - Помощна информация в Git Помощна информация в Git Ако се нуждаете от помощ за Git, има три еквивалентни начина да получите страницата с помощна информация (manpage) за всяка Git команда: $ git help <verb> $ git <verb> --help $ man git-<verb> Например, за повече информация за командата config, изпълнете: $ git help config Тези команди са полезни, защото имате достъп до тях винаги, дори когато сте офлайн. Ако помощните страници и тази книга не са достатъчни в специфични ситуации, можете да опитате \#git , \#github или #gitlab каналите на Libera Chat IRC сървъра на адрес https://libera.chat/ . Тези канали редовно са пълни със стотици потребители напреднали с Git и нямащи нищо против да помагат. В допълнение, ако не се нуждаете от пълната manpage документация, а само от кратко пояснение за опциите на конкретна команда, можете да използвате параметрите -h or --help така: $ git add -h usage: git add [<options>] [--] <pathspec>... -n, --dry-run dry run -v, --verbose be verbose -i, --interactive interactive picking -p, --patch select hunks interactively -e, --edit edit current diff and apply -f, --force allow adding otherwise ignored files -u, --update update tracked files --renormalize renormalize EOL of tracked files (implies -u) -N, --intent-to-add record only the fact that the path will be added later -A, --all add changes from all tracked and untracked files --ignore-removal ignore paths removed in the working tree (same as --no-all) --refresh don't add, only refresh the index --ignore-errors just skip files which cannot be added because of errors --ignore-missing check if - even missing - files are ignored in dry run --chmod (+|-)x override the executable bit of the listed files --pathspec-from-file <file> read pathspec from file --pathspec-file-nul with --pathspec-from-file, pathspec elements are separated with NUL character prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/ko/software/jira/service-management/resources | Jira Service Management 리소스 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 솔루션 사용 사례별 기능별 업계별 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 Back 가격 리소스 유형별 ITSM 제품 가이드 템플릿 추가 리소스 Back 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Jira Service Management는 이제 Service Collection의 일부가 되어 그 어느 때보다 강력해졌습니다. Rovo, 자산 및 새로운 Customer Service Management 앱으로 탁월한 서비스 경험을 제공하세요. 지금 사용해 보세요 Jira Service Management 리소스 라이브러리 최신 IT 서비스 관리의 기능 활용하기 주요 리소스 분석 보고서 The Forrester Wave TM : ESM, 2023에서 리더로 선정된 Atlassian 자세히 알아보기 비디오 Jira Service Management 주간 데모 자세히 알아보기 가이드 Jira Service Management 시작하기 자세히 알아보기 필터 | 초기화 형식 모든 형식 백서 및 전자책 분석 보고서 제품 가이드 사례 연구 제품 데모 아티클 동영상 및 웹 세미나 데이터시트 제품 업데이트 업계 보고서 토픽 모든 주제 자산 및 구성 관리 변경 관리 고객 서비스 관리 DevOps 엔터프라이즈 서비스 관리 인시던트 관리 ITSM Jira Service Management 서비스 요청 소식 스토리 / 필터 형식 모든 형식 모든 형식 백서 및 전자책 분석 보고서 제품 가이드 사례 연구 제품 데모 아티클 동영상 및 웹 세미나 데이터시트 제품 업데이트 업계 보고서 토픽 모든 주제 모든 주제 자산 및 구성 관리 변경 관리 고객 서비스 관리 DevOps 엔터프라이즈 서비스 관리 인시던트 관리 ITSM Jira Service Management 서비스 요청 소식 초기화 0 결과 × 가입하여 더 많은 문서와 자습서를 보세요. Thank you for subscribing 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/manage-tests/folders.html#content-wrapper | Folders | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Folders Folders Group related tests together in lightweight collections. Folders are a lightweight way to group a set of tests together. Managing Folders The Test List view on the Reflect main screen shows a list of all folders on the left side and a table of tests within the selected folder on the right. All accounts have at least one folder, the “All Tests” folder, which cannot be removed or renamed. You can create a new folder by clicking the “Add Folder” link at the bottom of the folders list. To rename a folder, click the pencil icon next to the folder name at the top of the Test List view. To delete a folder, click the “Delete Folder” button and accept the confirmation dialog. Changing a Test’s Folders You can modify the folders that contain a test from the Test Detail page. You can add a new folder within this view as well. In this section : Folders Managing Folders Changing a Test’s Folders Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://git-scm.com/book/it/v2/Per-Iniziare-Installing-Git | Git - Installing Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.5 Per Iniziare - Installing Git Installing Git Before you start using Git, you have to make it available on your computer. Even if it’s already installed, it’s probably a good idea to update to the latest version. You can either install it as a package or via another installer, or download the source code and compile it yourself. Nota This book was written using Git version 2.0.0 . Though most of the commands we use should work even in ancient versions of Git, some of them might not or might act slightly differently if you’re using an older version. Since Git is quite excellent at preserving backwards compatibility, any version after 2.0 should work just fine. Installing on Linux If you want to install Git on Linux via a binary installer, you can generally do so through the basic package-management tool that comes with your distribution. If you’re on Fedora for example, you can use yum: $ yum install git If you’re on a Debian-based distribution like Ubuntu, try apt-get: $ apt-get install git For more options, there are instructions for installing on several different Unix flavors on the Git website, at http://git-scm.com/download/linux . Installing on Mac There are several ways to install Git on a Mac. The easiest is probably to install the Xcode Command Line Tools. On Mavericks (10.9) or above you can do this simply by trying to run git from the Terminal the very first time. If you don’t have it installed already, it will prompt you to install it. If you want a more up to date version, you can also install it via a binary installer. An OSX Git installer is maintained and available for download at the Git website, at http://git-scm.com/download/mac . Figura 7. Git OS X Installer. You can also install it as part of the GitHub for Mac install. Their GUI Git tool has an option to install command line tools as well. You can download that tool from the GitHub for Mac website, at http://mac.github.com . Installing on Windows There are also a few ways to install Git on Windows. The most official build is available for download on the Git website. Just go to http://git-scm.com/download/win and the download will start automatically. Note that this is a project called Git for Windows (also called msysGit), which is separate from Git itself; for more information on it, go to http://msysgit.github.io/ . Another easy way to get Git installed is by installing GitHub for Windows. The installer includes a command line version of Git as well as the GUI. It also works well with Powershell, and sets up solid credential caching and sane CRLF settings. We’ll learn more about those things a little later, but suffice it to say they’re things you want. You can download this from the GitHub for Windows website, at http://windows.github.com . Installing from Source Some people may instead find it useful to install Git from source, because you’ll get the most recent version. The binary installers tend to be a bit behind, though as Git has matured in recent years, this has made less of a difference. If you do want to install Git from source, you need to have the following libraries that Git depends on: curl, zlib, openssl, expat, and libiconv. For example, if you’re on a system that has yum (such as Fedora) or apt-get (such as a Debian based system), you can use one of these commands to install all of the dependencies: $ yum install curl-devel expat-devel gettext-devel \ openssl-devel zlib-devel $ apt-get install libcurl4-gnutls-dev libexpat1-dev gettext \ libz-dev libssl-dev When you have all the necessary dependencies, you can go ahead and grab the latest tagged release tarball from several places. You can get it via the Kernel.org site, at https://www.kernel.org/pub/software/scm/git , or the mirror on the GitHub web site, at https://github.com/git/git/releases . It’s generally a little clearer what the latest version is on the GitHub page, but the kernel.org page also has release signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-1.9.1.tar.gz $ cd git-1.9.1 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc install-html install-info After this is done, you can also get Git via Git itself for updates: $ git clone git://git.kernel.org/pub/scm/git/git.git prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/ko/v2/Git%ec%9d%98-%ea%b8%b0%ec%b4%88-%ec%9a%94%ec%95%bd | Git - 요약 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 2.8 Git의 기초 - 요약 요약 이제 우리는 로컬에서 사용할 수 있는 Git 명령에 대한 기본 지식은 갖추었다. 저장소를 만들고 Clone 하는 방법, 수정하고 나서 Stage 하고 커밋하는 방법, 저장소의 히스토리를 조회하는 방법 등을 살펴보았다. 이어지는 장에서는 Git의 가장 강력한 기능인 브랜치 모델을 살펴볼 것이다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-%d0%bd%d0%b0-Git-%d0%9e%d0%b1%d0%be%d0%b1%d1%89%d0%b5%d0%bd%d0%b8%d0%b5 | Git - Обобщение About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 2.8 Основи на Git - Обобщение Обобщение В този момент, вие можете да правите всички базисни локални Git операции — създаване и клониране на хранилища, промени, подготвяне и публикуване на тези промени, и разглеждане на историята на промените в проекта във времето. Следва да разгледаме най-полезния аспект на Git - branching модела. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/ms/v2/Getting-Started-Getting-Help | Git - Getting Help About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.7 Getting Started - Getting Help Getting Help If you ever need help while using Git, there are three equivalent ways to get the comprehensive manual page (manpage) help for any of the Git commands: $ git help <verb> $ git <verb> --help $ man git-<verb> For example, you can get the manpage help for the git config command by running this: $ git help config These commands are nice because you can access them anywhere, even offline. If the manpages and this book aren’t enough and you need in-person help, you can try the #git , #github , or #gitlab channels on the Libera Chat IRC server, which can be found at https://libera.chat/ . These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help. In addition, if you don’t need the full-blown manpage help, but just need a quick refresher on the available options for a Git command, you can ask for the more concise “help” output with the -h option, as in: $ git add -h usage: git add [<options>] [--] <pathspec>... -n, --dry-run dry run -v, --verbose be verbose -i, --interactive interactive picking -p, --patch select hunks interactively -e, --edit edit current diff and apply -f, --force allow adding otherwise ignored files -u, --update update tracked files --renormalize renormalize EOL of tracked files (implies -u) -N, --intent-to-add record only the fact that the path will be added later -A, --all add changes from all tracked and untracked files --ignore-removal ignore paths removed in the working tree (same as --no-all) --refresh don't add, only refresh the index --ignore-errors just skip files which cannot be added because of errors --ignore-missing check if - even missing - files are ignored in dry run --chmod (+|-)x override the executable bit of the listed files --pathspec-from-file <file> read pathspec from file --pathspec-file-nul with --pathspec-from-file, pathspec elements are separated with NUL character prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/ms/v2/Distributed-Git-Contributing-to-a-Project | Git - Contributing to a Project About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Distributed Git - Contributing to a Project Contributing to a Project The main difficulty with describing how to contribute to a project are the numerous variations on how to do that. Because Git is very flexible, people can and do work together in many ways, and it’s problematic to describe how you should contribute — every project is a bit different. Some of the variables involved are active contributor count, chosen workflow, your commit access, and possibly the external contribution method. The first variable is active contributor count — how many users are actively contributing code to this project, and how often? In many instances, you’ll have two or three developers with a few commits a day, or possibly less for somewhat dormant projects. For larger companies or projects, the number of developers could be in the thousands, with hundreds or thousands of commits coming in each day. This is important because with more and more developers, you run into more issues with making sure your code applies cleanly or can be easily merged. Changes you submit may be rendered obsolete or severely broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next variable is the workflow in use for the project. Is it centralized, with each developer having equal write access to the main codeline? Does the project have a maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your work to them first? The next variable is your commit access. The workflow required in order to contribute to a project is much different if you have write access to the project than if you don’t. If you don’t have write access, how does the project prefer to accept contributed work? Does it even have a policy? How much work are you contributing at a time? How often do you contribute? All these questions can affect how you contribute effectively to a project and what workflows are preferred or available to you. We’ll cover aspects of each of these in a series of use cases, moving from simple to more complex; you should be able to construct the specific workflows you need in practice from these examples. Commit Guidelines Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file. First, your submissions should not contain any whitespace errors. Git provides an easy way to check for this — before you commit, run git diff --check , which identifies possible whitespace errors and lists them for you. Figure 56. Output of git diff --check If you run that command before committing, you can tell if you’re about to commit whitespace issues that may annoy other developers. Next, try to make each commit a logically separate changeset. If you can, try to make your changes digestible — don’t code for a whole weekend on five different issues and then submit them all as one massive commit on Monday. Even if you don’t commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit. If some of the changes modify the same file, try to use git add --patch to partially stage files (covered in detail in Interactive Staging ). The project snapshot at the tip of the branch is identical whether you do one commit or five, as long as all the changes are added at some point, so try to make things easier on your fellow developers when they have to review your changes. This approach also makes it easier to pull out or revert one of the changesets if you need to later. Rewriting History describes a number of useful Git tricks for rewriting history and interactively staging files — use these tools to help craft a clean and understandable history before sending the work to someone else. The last thing to keep in mind is the commit message. Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior — this is a good guideline to follow. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." Here is a template you can follow, which we’ve lightly adapted from one originally written by Tim Pope : Capitalized, short (50 chars or less) summary More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase will confuse you if you run the two together. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like git merge and git revert. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, followed by a single space, with blank lines in between, but conventions vary here - Use a hanging indent If all your commit messages follow this model, things will be much easier for you and the developers with whom you collaborate. The Git project has well-formatted commit messages — try running git log --no-merges there to see what a nicely-formatted project-commit history looks like. Note Do as we say, not as we do. For the sake of brevity, many of the examples in this book don’t have nicely-formatted commit messages like this; instead, we simply use the -m option to git commit . In short, do as we say, not as we do. Private Small Team The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository. In this environment, you can follow a workflow similar to what you might do when using Subversion or another centralized system. You still get the advantages of things like offline committing and vastly simpler branching and merging, but the workflow can be very similar; the main difference is that merges happen client-side rather than on the server at commit time. Let’s see what it might look like when two developers start to work together with a shared repository. The first developer, John, clones the repository, makes a change, and commits locally. The protocol messages have been replaced with … in these examples to shorten them somewhat. # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'Remove invalid default value' [master 738ee87] Remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) The second developer, Jessica, does the same thing — clones the repository and commits a change: # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'Add reset task' [master fbff5bc] Add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Now, Jessica pushes her work to the server, which works just fine: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master The last line of the output above shows a useful return message from the push operation. The basic format is <oldref>..<newref> fromref → toref , where oldref means the old reference, newref means the new reference, fromref is the name of the local reference being pushed, and toref is the name of the remote reference being updated. You’ll see similar output like this below in the discussions, so having a basic idea of the meaning will help in understanding the various states of the repositories. More details are available in the documentation for git-push . Continuing with this example, shortly afterwards, John makes some changes, commits them to his local repository, and tries to push them to the same server: # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' In this case, John’s push fails because of Jessica’s earlier push of her changes. This is especially important to understand if you’re used to Subversion, because you’ll notice that the two developers didn’t edit the same file. Although Subversion automatically does such a merge on the server if different files are edited, with Git, you must first merge the commits locally. In other words, John must first fetch Jessica’s upstream changes and merge them into his local repository before he will be allowed to push. As a first step, John fetches Jessica’s work (this only fetches Jessica’s upstream work, it does not yet merge it into John’s work): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master At this point, John’s local repository looks something like this: Figure 57. John’s divergent history Now John can merge Jessica’s work that he fetched into his own local work: $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) As long as that local merge goes smoothly, John’s updated history will now look like this: Figure 58. John’s repository after merging origin/master At this point, John might want to test this new code to make sure none of Jessica’s work affects any of his and, as long as everything seems fine, he can finally push the new merged work up to the server: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master In the end, John’s commit history will look like this: Figure 59. John’s history after pushing to the origin server In the meantime, Jessica has created a new topic branch called issue54 , and made three commits to that branch. She hasn’t fetched John’s changes yet, so her commit history looks like this: Figure 60. Jessica’s topic branch Suddenly, Jessica learns that John has pushed some new work to the server and she wants to take a look at it, so she can fetch all new content from the server that she does not yet have with: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master That pulls down the work John has pushed up in the meantime. Jessica’s history now looks like this: Figure 61. Jessica’s history after fetching John’s changes Jessica thinks her topic branch is ready, but she wants to know what part of John’s fetched work she has to merge into her work so that she can push. She runs git log to find out: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 Remove invalid default value The issue54..origin/master syntax is a log filter that asks Git to display only those commits that are on the latter branch (in this case origin/master ) that are not on the first branch (in this case issue54 ). We’ll go over this syntax in detail in Commit Ranges . From the above output, we can see that there is a single commit that John has made that Jessica has not merged into her local work. If she merges origin/master , that is the single commit that will modify her local work. Now, Jessica can merge her topic work into her master branch, merge John’s work ( origin/master ) into her master branch, and then push back to the server again. First (having committed all of the work on her issue54 topic branch), Jessica switches back to her master branch in preparation for integrating all this work: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jessica can merge either origin/master or issue54 first — they’re both upstream, so the order doesn’t matter. The end snapshot should be identical no matter which order she chooses; only the history will be different. She chooses to merge the issue54 branch first: $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) No problems occur; as you can see it was a simple fast-forward merge. Jessica now completes the local merging process by merging John’s earlier fetched work that is sitting in the origin/master branch: $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Everything merges cleanly, and Jessica’s history now looks like this: Figure 62. Jessica’s history after merging John’s changes Now origin/master is reachable from Jessica’s master branch, so she should be able to successfully push (assuming John hasn’t pushed even more changes in the meantime): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Each developer has committed a few times and merged each other’s work successfully. Figure 63. Jessica’s history after pushing all changes back to the server That is one of the simplest workflows. You work for a while (generally in a topic branch), and merge that work into your master branch when it’s ready to be integrated. When you want to share that work, you fetch and merge your master from origin/master if it has changed, and finally push to the master branch on the server. The general sequence is something like this: Figure 64. General sequence of events for a simple multiple-developer Git workflow Private Managed Team In this next scenario, you’ll look at contributor roles in a larger private group. You’ll learn how to work in an environment where small groups collaborate on features, after which those team-based contributions are integrated by another party. Let’s say that John and Jessica are working together on one feature (call this “featureA”), while Jessica and a third developer, Josie, are working on a second (say, “featureB”). In this case, the company is using a type of integration-manager workflow where the work of the individual groups is integrated only by certain engineers, and the master branch of the main repo can be updated only by those engineers. In this scenario, all work is done in team-based branches and pulled together by the integrators later. Let’s follow Jessica’s workflow as she works on her two features, collaborating in parallel with two different developers in this environment. Assuming she already has her repository cloned, she decides to work on featureA first. She creates a new branch for the feature and does some work on it there: # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'Add limit to log function' [featureA 3300904] Add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) At this point, she needs to share her work with John, so she pushes her featureA branch commits up to the server. Jessica doesn’t have push access to the master branch — only the integrators do — so she has to push to another branch in order to collaborate with John: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica emails John to tell him that she’s pushed some work into a branch named featureA and he can look at it now. While she waits for feedback from John, Jessica decides to start working on featureB with Josie. To begin, she starts a new feature branch, basing it off the server’s master branch: # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Now, Jessica makes a couple of commits on the featureB branch: $ vim lib/simplegit.rb $ git commit -am 'Make ls-tree function recursive' [featureB e5b0fdc] Make ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'Add ls-files' [featureB 8512791] Add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Jessica’s repository now looks like this: Figure 65. Jessica’s initial commit history She’s ready to push her work, but gets an email from Josie that a branch with some initial “featureB” work on it was already pushed to the server as the featureBee branch. Jessica needs to merge those changes with her own before she can push her work to the server. Jessica first fetches Josie’s changes with git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Assuming Jessica is still on her checked-out featureB branch, she can now merge Josie’s work into that branch with git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) At this point, Jessica wants to push all of this merged “featureB” work back to the server, but she doesn’t want to simply push her own featureB branch. Rather, since Josie has already started an upstream featureBee branch, Jessica wants to push to that branch, which she does with: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee This is called a refspec . See The Refspec for a more detailed discussion of Git refspecs and different things you can do with them. Also notice the -u flag; this is short for --set-upstream , which configures the branches for easier pushing and pulling later. Suddenly, Jessica gets email from John, who tells her he’s pushed some changes to the featureA branch on which they are collaborating, and he asks Jessica to take a look at them. Again, Jessica runs a simple git fetch to fetch all new content from the server, including (of course) John’s latest work: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessica can display the log of John’s new work by comparing the content of the newly-fetched featureA branch with her local copy of the same branch: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 Increase log output to 30 from 25 If Jessica likes what she sees, she can merge John’s new work into her local featureA branch with: $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Finally, Jessica might want to make a couple minor changes to all that merged content, so she is free to make those changes, commit them to her local featureA branch, and push the end result back to the server: $ git commit -am 'Add small tweak to merged content' [featureA 774b3ed] Add small tweak to merged content 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Jessica’s commit history now looks something like this: Figure 66. Jessica’s history after committing on a feature branch At some point, Jessica, Josie, and John inform the integrators that the featureA and featureBee branches on the server are ready for integration into the mainline. After the integrators merge these branches into the mainline, a fetch will bring down the new merge commit, making the history look like this: Figure 67. Jessica’s history after merging both her topic branches Many groups switch to Git because of this ability to have multiple teams working in parallel, merging the different lines of work late in the process. The ability of smaller subgroups of a team to collaborate via remote branches without necessarily having to involve or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 68. Basic sequence of this managed-team workflow Forked Public Project Contributing to public projects is a bit different. Because you don’t have the permissions to directly update branches on the project, you have to get the work to the maintainers some other way. This first example describes contributing via forking on Git hosts that support easy forking. Many hosting sites support this (including GitHub, BitBucket, repo.or.cz, and others), and many project maintainers expect this style of contribution. The next section deals with projects that prefer to accept contributed patches via email. First, you’ll probably want to clone the main repository, create a topic branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Note You may want to use rebase -i to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review — see Rewriting History for more information about interactive rebasing. When your branch work is finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository URL as a new remote of your local repository; in this example, let’s call it myfork : $ git remote add myfork <url> You then need to push your new work to this repository. It’s easiest to push the topic branch you’re working on to your forked repository, rather than merging that work into your master branch and pushing that. The reason is that if your work isn’t accepted or is cherry-picked, you don’t have to rewind your master branch (the Git cherry-pick operation is covered in more detail in Rebasing and Cherry-Picking Workflows ). If the maintainers merge , rebase , or cherry-pick your work, you’ll eventually get it back via pulling from their repository anyhow. In any event, you can push your work with: $ git push -u myfork featureA Once your work has been pushed to your fork of the repository, you need to notify the maintainers of the original project that you have work you’d like them to merge. This is often called a pull request , and you typically generate such a request either via the website — GitHub has its own “Pull Request” mechanism that we’ll go over in GitHub — or you can run the git request-pull command and email the subsequent output to the project maintainer manually. The git request-pull command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and produces a summary of all the changes you’re asking to be pulled. For instance, if Jessica wants to send John a pull request, and she’s done two commits on the topic branch she just pushed, she can run this: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): Create new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): Add limit to log function Increase log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) This output can be sent to the maintainer — it tells them where the work was branched from, summarizes the commits, and identifies from where the new work is to be pulled. On a project for which you’re not the maintainer, it’s generally easier to have a branch like master always track origin/master and to do your work in topic branches that you can easily discard if they’re rejected. Having work themes isolated into topic branches also makes it easier for you to rebase your work if the tip of the main repository has moved in the meantime and your commits no longer apply cleanly. For example, if you want to submit a second topic of work to the project, don’t continue working on the topic branch you just pushed up — start over from the main repository’s master branch: $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Now, each of your topics is contained within a silo — similar to a patch queue — that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so: Figure 69. Initial commit history with featureB work Let’s say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges. In this case, you can try to rebase that branch on top of origin/master , resolve the conflicts for the maintainer, and then resubmit your changes: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA This rewrites your history to now look like Commit history after featureA work . Figure 70. Commit history after featureA work Because you rebased the branch, you have to specify the -f to your push command in order to be able to replace the featureA branch on the server with a commit that isn’t a descendant of it. An alternative would be to push this new work to a different branch on the server (perhaps called featureAv2 ). Let’s look at one more possible scenario: the maintainer has looked at work in your second branch and likes the concept but would like you to change an implementation detail. You’ll also take this opportunity to move the work to be based off the project’s current master branch. You start a new branch based off the current origin/master branch, squash the featureB changes there, resolve any conflicts, make the implementation change, and then push that as a new branch: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 The --squash option takes all the work on the merged branch and squashes it into one changeset producing the repository state as if a real merge happened, without actually making a merge commit. This means your future commit will have one parent only and allows you to introduce all the changes from another branch and then make more changes before recording the new commit. Also the --no-commit option can be useful to delay the merge commit in case of the default merge process. At this point, you can notify the maintainer that you’ve made the requested changes, and that they can find those changes in your featureBv2 branch. Figure 71. Commit history after featureBv2 work Public Project over Email Many projects have established procedures for accepting patches — you’ll need to check the specific rules for each project, because they will differ. Since there are several older, larger projects which accept patches via a developer mailing list, we’ll go over an example of that now. The workflow is similar to the previous use case — you create topic branches for each patch series you work on. The difference is how you submit them to the project. Instead of forking the project and pushing to your own writable version, you generate email versions of each commit series and email them to the developer mailing list: $ git checkout -b topicA ... work ... $ git commit ... work ... $ git commit Now you have two commits that you want to send to the mailing list. You use git format-patch to generate the mbox-formatted files that you can email to the list — it turns each commit into an email message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body. The nice thing about this is that applying a patch from an email generated with format-patch preserves all the commit information properly. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch The format-patch command prints out the names of the patch files it creates. The -M switch tells Git to look for renames. The files end up looking like this: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] Add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 You can also edit these patch files to add more information for the email list that you don’t want to show up in the commit message. If you add text between the --- line and the beginning of the patch (the diff --git line), the developers can read it, but that content is ignored by the patching process. To email this to a mailing list, you can either paste the file into your email program or send it via a command-line program. Pasting the text often causes formatting issues, especially with “smarter” clients that don’t preserve newlines and other whitespace appropriately. Luckily, Git provides a tool to help you send properly formatted patches via IMAP, which may be easier for you. We’ll demonstrate how to send a patch via Gmail, which happens to be the email agent we know best; you can read detailed instructions for a number of mail programs at the end of the aforementioned Documentation/SubmittingPatches file in the Git source code. First, you need to set up the imap section in your ~/.gitconfig file. You can set each value separately with a series of git config commands, or you can add them manually, but in the end your config file should look something like this: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false If your IMAP server doesn’t use SSL, the last two lines probably aren’t necessary, and the host value will be imap:// instead of imaps:// . When that is set up, you can use git imap-send to place the patch series in the Drafts folder of the specified IMAP server: $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you’re sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off. You can also send the patches through an SMTP server. As before, you can set each value separately with a series of git config commands, or you can add them manually in the sendemail section in your ~/.gitconfig file: [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 After this is done, you can use git send-email to send your patches: $ git send-email *.patch 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Then, Git spits out a bunch of log information looking something like this for each patch you’re sending: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] Add limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Tip For help on configuring your system and email, more tips and tricks, and a sandbox to send a trial patch via email, go to git-send-email.io . Summary In this section, we covered multiple workflows, and talked about the differences between working as part of a small team on closed-source projects vs contributing to a big public project. You know to check for white-space errors before committing, and can write a great commit message. You learned how to format patches, and e-mail them to a developer mailing list. Dealing with merges was also covered in the context of the different workflows. You are now well prepared to collaborate on any project. Next, you’ll see how to work the other side of the coin: maintaining a Git project. You’ll learn how to be a benevolent dictator or integration manager. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://support.smartbear.com/reflect/docs/en/manage-tests/folders.html#folders | Folders | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Manage Tests Folders Folders Group related tests together in lightweight collections. Folders are a lightweight way to group a set of tests together. Managing Folders The Test List view on the Reflect main screen shows a list of all folders on the left side and a table of tests within the selected folder on the right. All accounts have at least one folder, the “All Tests” folder, which cannot be removed or renamed. You can create a new folder by clicking the “Add Folder” link at the bottom of the folders list. To rename a folder, click the pencil icon next to the folder name at the top of the Test List view. To delete a folder, click the “Delete Folder” button and accept the confirmation dialog. Changing a Test’s Folders You can modify the folders that contain a test from the Test Detail page. You can add a new folder within this view as well. In this section : Folders Managing Folders Changing a Test’s Folders Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:44 |
https://git-scm.com/book/zh-tw/v2/%e9%96%8b%e5%a7%8b-%e5%8f%96%e5%be%97%e8%aa%aa%e6%98%8e%e6%96%87%e4%bb%b6 | Git - 取得說明文件 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.7 開始 - 取得說明文件 取得說明文件 若讀者在使用 Git 時需要幫助，有三種取得 Git 命令說明文件的方法： $ git help <verb> $ git <verb> --help $ man git-<verb> 例如：讀者可以下列命令取得 config 命令的說明文件 $ git help config 這些指令的優點是你可以隨時使用它們，甚至是你沒有連上網路的時候。 若說明文件及這本書不足以幫助讀者，且讀者需要更進一步的協助，可試著進入 Freenode IRC 伺服器（irc.freenode.net）的 #git 或 #github 頻道。 這些頻道平時都有上百位對 Git 非常瞭解的高手，而且通常樂意協助。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/uk/v2/%d0%92%d1%81%d1%82%d1%83%d0%bf-%d0%a2%d1%80%d0%b8-%d1%81%d1%82%d0%b0%d0%bd%d0%b8 | Git - Три стани About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 1.5 Вступ - Три стани Три стани Тепер будьте уважні — це найважливіша річ, яку потрібно запам’ятати, якщо ви хочете щоб подальше вивчення Git пройшло гладко. Git має три основних стани, в яких можуть перебувати ваші файли: збережений у коміті (commited), змінений (modified) та індексований (staged): Збережений у коміті означає, що дані безпечно збережено в локальній базі даних. Змінений означає, що у файл внесено редагування, які ще не збережено в базі даних. Індексований стан виникає тоді, коли ви позначаєте змінений файл у поточній версії, щоб ці зміни ввійшли до наступного знімку коміту. З цього випливають три основні частини проекту під управлінням Git: директорія Git, робоче дерево та індекс. Рисунок 6. Робоча директорія, індекс та директорія Git. У директорії Git система зберігає метадані та базу даних об’єктів вашого проекту. Це найважливіша частина Git, саме вона копіюється при клонуванні сховища з іншого комп’ютеру. Робоче дерево — це одна окрема версія проекту, взята зі сховища. Ці файли видобуваються з бази даних у теці Git та розміщуються на диску для подальшого використання та редагування. Індекс — це файл, що зазвичай знаходиться в директорії Git і містить інформацію про те, що буде збережено у наступному коміті. Також цей файл називають областю додавання'' (staging area), проте ми переважно будемо користуватись технічним терміном Git індекс''. Найпростіший процес взаємодії з Git виглядає приблизно так: Ви редагуєте файли у своїй робочій директорії. Вибірково надсилаєте до індексу лише ті зміни, що їх ви бажаєте зберегти в наступному коміті, і лише ці зміни буде збережено в індексі. Створюєте коміт: знімок з індексу остаточно зберігається в директорії Git. У випадку, якщо окрема версія файлу вже є в директорії Git, цей файл вважається збереженим у коміті. Якщо він зазнав змін і перебуває в індексі, то він індексований. Якщо ж його стан відрізняється від того, який був у коміті, і файл не знаходиться в індексі, то він називається зміненим. У Основи Git ви дізнаєтесь більше про ці стани, а також про те, як використовувати їхні переваги або взагалі пропускати етап індексу. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%9c%d0%b0%d0%bd%d0%b8%d0%bf%d1%83%d0%bb%d0%b0%d1%86%d0%b8%d1%8f-%d0%bd%d0%b0-%d0%b8%d1%81%d1%82%d0%be%d1%80%d0%b8%d1%8f%d1%82%d0%b0 | Git - Манипулация на историята About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.6 Git инструменти - Манипулация на историята Манипулация на историята Често в работата си с Git може да поискате да ревизирате историята на локалните къмити. Една от чудесните страни на Git е, че ви позволява да вземате решения в последния възможен момент. Вие решавате кои файлове в кои къмити да отидат непосредствено преди къмитване с индексната област, вие може да решите, че в момента отлагате работата по даде проблем с git stash и също така, можете да презапишете предишни къмити така че да изглеждат сякаш са се случили по различен начин. Това може да включва смяна на реда на къмитите, смяна на съобщенията или модифициране на файлове в къмит, комбиниране на няколко в един или разделяне на къмит на части или пък изтриване на къмит — всичко това преди да споделите работата си с колегите. В тази част от книгата ще видим как се осъществяват такива задачи, така че да накарате историята на работата ви да изглежда по начина, по който вие искате преди да я споделите с другите. Забележка Не публикувайте работата си преди да сте я довършили докрай Едно от кардиналните правила на Git е това, че понеже вършите повечето работа локално във вашето копие на хранилището, вие разполагате с почти неограничена свобода да преправяте локалната си история. Обаче, след като веднъж сте публикували работата си, нещата значително се променят и е редно да гледате на нея като на финална версия, освен ако нямате наистина добра причина да промените това. Накратко, би следвало да избягвате да публикувате работата си до момента в който решите, че тя е достатъчно добра за да бъде споделена с другите. Промяна на последния къмит Промяната на най-последния къмит вероятно е най-често срещания вид манипулация на историята. Две неща ще искате да правите най-често: просто да редактирате къмит съобщението или да промените съдържанието на къмита добавяйки, изтривайки или променяйки файлове. Ако става дума само за съобщението на последния къмит, това е лесно: $ git commit --amend Командата зарежда съобщението на къмита в текстовия редактор, където можете да го редактирате, да запишете промените и да излезете. Когато затворите редактора, той записва нов къмит с редактираното съобщение и го прави последен къмит. Ако, от друга страна, искате да промените нещо по действителното съдържание на къмита, процесът в общи линии работи по същия начин — първо направете желаните промени, индексирайте ги и след това git commit --amend командата ще замени последния записан къмит с вашите нови, коригирани данни. Трябва да внимавате с тази техника, понеже тя променя SHA-1 хеша на къмита. Това е като много малко пребазиране — не променяйте последния къмит, ако вече сте го публикували! Подсказка Редактиран къмит може да се нуждае, но може и да не се нуждае от amended къмит съобщение Когато редактирате къмит, имате възможност да смените както съобщението, така и съдържанието на данните в къмита. Ако променяте данните по същество, почти винаги е добре да обновите и съобщението, така че да отразява корекциите. От друга страна, ако промените са тривиални (например поправка на правописна грешка или добавяне на файл, който сте забравили да индексирате) и оригиналното съобщение си е съвсем на място, можете просто да направите промените и да прескочите стъпката с редактора изцяло: $ git commit --amend --no-edit Смяна на повече къмит съобщения За да промените къмит, който е назад в историята, ще ви трябват по-сложни инструменти. Git не разполага с инструмент за модифициране на историята, но можете да използвате rebase за да пребазирате серия от къмити върху HEAD-а, на който са били първоначално базирани, вместо да ги премествате към друг. С интерактивния инструмент за пребазиране след това можете да спирате на всеки къмит, който искате и да редактирате съобщението му, да добавяте файлове и т.н. Можете да стартирате rebase в интерактивен режим с флага -i на командата git rebase . Трябва да посочите колко назад искате да презаписвате къмити указвайки на командата върху кой къмит да пребазира. Например, ако искате да промените последните три къмит съобщения или кое да е съобщение в тази група, вие подавате като аргумент на git rebase -i родителя на последния къмит, който искате да редактирате, което е HEAD~2^ или HEAD~3 . Може да е по-лесно да използвате ~3 , понеже опитвате да редактирате последните три къмита, но имайте предвид, че всъщност посочвате четири къмита назад, родителя на последния къмит, който искате да промените: $ git rebase -i HEAD~3 Подчертаваме отново, че това е пребазираща команда — всеки къмит в обхвата HEAD~3..HEAD с променено съобщение и всички негови наследници ще бъдат презаписани. Не включвайте никакъв къмит, който вече сте изпратили на централния сървър — правейки това ще смутите другите разработчици, защото осигурявате алтернативна версия на една и съща промяна. Изпълнявайки командата, получавате списък къмити в текстовия си редакто, подобно на това: pick f7f3f6d Change my name a bit pick 310154e Update README formatting and add blame pick a5f4a0d Add cat-file # Rebase 710f0f8..a5f4a0d onto 710f0f8 # # Commands: # p, pick <commit> = use commit # r, reword <commit> = use commit, but edit the commit message # e, edit <commit> = use commit, but stop for amending # s, squash <commit> = use commit, but meld into previous commit # f, fixup <commit> = like "squash", but discard this commit's log message # x, exec <command> = run command (the rest of the line) using shell # b, break = stop here (continue rebase later with 'git rebase --continue') # d, drop <commit> = remove commit # l, label <label> = label current HEAD with a name # t, reset <label> = reset HEAD to a label # m, merge [-C <commit> | -c <commit>] <label> [# <oneline>] # . create a merge commit using the original merge commit's # . message (or the oneline, if no original merge commit was # . specified). Use -c <commit> to reword the commit message. # # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST. # # However, if you remove everything, the rebase will be aborted. # # Note that empty commits are commented out Важно е да кажем, че къмитите се изброяват в обратен ред на този, в който се виждат с log командата. Ако изпълните log , виждате нещо такова: $ git log --pretty=format:"%h %s" HEAD~3..HEAD a5f4a0d Add cat-file 310154e Update README formatting and add blame f7f3f6d Change my name a bit Забележете обърнатия ред. Интерактивното пребазиране ви дава скрипта, който ще изпълни. То ще започне от къмита, който указвате на командния ред ( HEAD~3 ) и ще извърши промените въведени във всеки от тези къмити отгоре надолу. Най-старият се показва най-отгоре, защото той е първият, който ще бъде приложен. Трябва да редактирате скрипта така, че да спре на къмита, който желаете да редактирате. За да направите това, променете думата “pick” на “edit” за всеки от къмитите, след които искате скрипта да спре. Например, за да промените само третото къмит съобщение, променяте файла да изглежда така: edit f7f3f6d Change my name a bit pick 310154e Update README formatting and add blame pick a5f4a0d Add cat-file Когато запишете и излезете от редактора, Git ви превърта обратно до последния къмит в този списък и ви връща в командния ред със следното съобщение: $ git rebase -i HEAD~3 Stopped at f7f3f6d... Change my name a bit You can amend the commit now, with git commit --amend Once you're satisfied with your changes, run git rebase --continue Инструкциите посочват точно какво да направите. Напишете: $ git commit --amend Променете съобщението на къмита и затворете редактора. След това изпълнете: $ git rebase --continue Тази команда ще приложи останалите два къмита автоматично и след това сте готови. Ако смените думата pick с edit на повече редове, можете да повторите тези стъпки за всеки съответен къмит. Всеки път Git ще спира, ще ви позволи да промените къмита и ще продължи, когато сте готови. Пренареждане на къмити Можете да използвате интерактивното пребазиране за да размествате или изцяло да премахвате къмити. Ако искате да премахнете къмита “added cat-file” и да смените реда, в който останалите два се прилагат, може да смените rebase скрипта от това: pick f7f3f6d Change my name a bit pick 310154e Update README formatting and add blame pick a5f4a0d Add cat-file към това: pick 310154e Update README formatting and add blame pick f7f3f6d Change my name a bit Когато запишете и затворите редактора, Git превърта клона назад до родителя на тези къмити, прилага 310154e следван от f7f3f6d и спира. Сега редът на двата останали къмита е сменен, а “added cat-file” е изцяло премахнат. Обединяване на къмити Възможно е също така да вземете няколко къмита и да ги обедините в един единичен. Процесът е известен като Squashing и също може да се направи с инструмента за интерактивно пребазиране. Скриптът ви дава напътствия в rebase съобщението: # # Commands: # p, pick <commit> = use commit # r, reword <commit> = use commit, but edit the commit message # e, edit <commit> = use commit, but stop for amending # s, squash <commit> = use commit, but meld into previous commit # f, fixup <commit> = like "squash", but discard this commit's log message # x, exec <command> = run command (the rest of the line) using shell # b, break = stop here (continue rebase later with 'git rebase --continue') # d, drop <commit> = remove commit # l, label <label> = label current HEAD with a name # t, reset <label> = reset HEAD to a label # m, merge [-C <commit> | -c <commit>] <label> [# <oneline>] # . create a merge commit using the original merge commit's # . message (or the oneline, if no original merge commit was # . specified). Use -c <commit> to reword the commit message. # # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST. # # However, if you remove everything, the rebase will be aborted. # # Note that empty commits are commented out В този случай, ако вместо “pick” или “edit”, укажете “squash”, Git прилага текущата промяната и промяната непосредствено преди нея и ви позволява да слеете къмит съобщенията заедно. Така че, ако искате да направите единичен къмит от горните три, може да редактирате скрипта си така: pick f7f3f6d Change my name a bit squash 310154e Update README formatting and add blame squash a5f4a0d Add cat-file Когато затворите редактора, Git прилага всичките три промени и пуска редактора още веднъж, за сливане на трите съобщения: # This is a combination of 3 commits. # The first commit's message is: Change my name a bit # This is the 2nd commit message: Update README formatting and add blame # This is the 3rd commit message: Add cat-file Записвайки това, вие получавате единичен къмит, който съдържа промените от всичките три предишни. Разделяне на къмит Разделянето ще отмени даден къмит и след това частично ще индексира и къмитне толкова пъти, колкото укажете. Например, решавате да разделите втория от трите къмита по-горе. Вместо “Update README formatting and add blame”, искате да го разделите в два къмита със съобщения “Updated README formatting” за първия и “Add blame” за втория. Можете да го постигнете с rebase -i скрипта променяйки инструкцията на втория къмит на “edit”: pick f7f3f6d Change my name a bit edit 310154e Update README formatting and add blame pick a5f4a0d Add cat-file След това, когато скриптът ви върне в командния ред, вие reset-вате къмита, вземате промените, които са били отменени и създавате няколко къмита от тях. Когато запишете и затворите редактора, Git превърта назад до родителя на първия къмит в списъка, прилага първия къмит ( f7f3f6d ), прилага втория ( 310154e ) и ви връща в конзолата. Там можете да направите mixed reset на този къмит с командата git reset HEAD^ , което на практика отменя къмита и оставя модифицираните файлове извън индекса. Сега можете да индексирате и къмитвате файлове докато получите колкото желаете къмита и след това да изпълните git rebase --continue за да завършите процеса: $ git reset HEAD^ $ git add README $ git commit -m 'Update README formatting' $ git add lib/simplegit.rb $ git commit -m 'Add blame' $ git rebase --continue Git ще приложи и последния къмит от скрипта ( a5f4a0d ) и сега историята ви изглежда така: $ git log -4 --pretty=format:"%h %s" 1c002dd Add cat-file 9b29157 Add blame 35cfb2b Update README formatting f7f3f6d Change my name a bit Този процес променя SHA-1 стойностите за последните 3 най-нови къмита в списъка, така че се убедете, че никой от тях не е бил публикуван в споделено хранилище. Отбележете също така, че последният къмит в списъка ( f7f3f6d ) е непроменен. Въпреки, че е показан в скрипта, Git го оставя непроменен, понеже той е маркиран като “pick” и е приложен преди всички rebase промени. Изтриване на къмит Ако искате да изтриете къмит, можете да го направите със скрипта rebase -i . В списъка с къмити, поставете думата “drop” пред този, който искате да изтриете (или просто изтрийте реда от rebase скрипта): pick 461cb2a This commit is OK drop 5aecc10 This commit is broken Поради начина, по който Git построява къмит обектите, изтриването или промяната на къмит предизвиква презапис на всички следващи след него. Колкото по-назад в историята се връщате, толкова повече къмити ще трябва да се създадат наново. Това може да предизвика купища merge конфликти, ако по-късно в историята има много къмити, зависещи от изтрития. Ако в един момент в rebase процеса установите, че той не е бил добра идея, можете винаги да спрете. Изпълнете git rebase --abort и хранилището ще се върне в статуса, в което е било преди да стартирате пребазирането. Ако в края на пребазирането решите, че резултатът не е какъвто очаквате, можете да използвате git reflog за да възстановите по-ранна версия на клона. Вижте Възстановяване на данни за повече информация за командата reflog . Забележка Drew DeVault е създал практическо hands-on упътване с упражнения за използването на git rebase . Достъпно е на адрес: https://git-rebase.io/ Мощната алтернатива: filter-branch Съществува и друга опция за презапис на историята, която се използва за модифициране на голям брой къмити в в скриптов маниер — например ако искате да си смените имейл адреса глобално или да премахнете файл от всеки къмит. Командата е filter-branch и може да променя огромни порции от вашата история, така че вероятно не би следвало да я ползвате — освен ако проектът ви все още не е публично достъпен или пък никой ваш колега не е базирал работата си на някой от вашите къмити, които ще бъдат пренаписани. Обаче, командата може да бъде много полезна. Ще покажем няколко от най-честите ѝ приложения, така че да получите идея какво може да прави. Внимание git filter-branch има много недостатъци и вече не се препоръчва като начин за презапис на историята. Вместо това, използвайте git-filter-repo , която е скрипт на Python и върши по-добра работа в ситуациите, в които нормално бихте използвали filter-branch . Документацията и сорс кода ѝ могат да се намерят на https://github.com/newren/git-filter-repo . Изтриване на файл от всеки къмит Това се налага доста често. Някой по невнимание къмитва голям двоичен файл с git add . и се налага да го махнете навсякъде. Или пък, без да искате сте къмитнали файл, съдържащ парола, а проектът трябва да стане с отворен код. В такива случаи filter-branch е инструментът, който вероятно ще искате да използвате, за да ремонтирате историята из основи. За да премахнете файла passwords.txt от цялата история използвайте параметъра --tree-filter на filter-branch : $ git filter-branch --tree-filter 'rm -f passwords.txt' HEAD Rewrite 6b9b3cf04e7c5686a9cb838c3f36a8cb6a0fc2bd (21/21) Ref 'refs/heads/master' was rewritten Опцията --tree-filter изпълнява указаната команда след всяко извличане на съдържанието на проекта и след това къмитва резултатите обратно. В този случай, вие изтривате файла passwords.txt от всеки един snapshot без значение дали присъства или не. Ако искате да премахнете всички случайно къмитнати backup файлове от вашия редактор, може да изпълните нещо като git filter-branch --tree-filter 'rm -f *~' HEAD . Ще видите как Git пренаписва дърветата и къмитите и след това премества указателя на клона в края. Добра идея е да направите това пробно в тестов клон и ако резултатите ви устройват, да го приложите и в master клона като му направите hard-reset. Можете да пуснете filter-branch и върху всички клонове с опцията --all към командата. Превръщане на под-директория в Root директория Да допуснем, че сте импортирали проект от друга source control система и имате под-директории, които са излишни ( trunk , tags и т.н.). Ако искате да направите директорията trunk корен за проекта ви за всеки къмит, също може да използвате filter-branch : $ git filter-branch --subdirectory-filter trunk HEAD Rewrite 856f0bf61e41a27326cdae8f09fe708d679f596f (12/12) Ref 'refs/heads/master' was rewritten Сега trunk е новата основна директория. Git автоматично ще премахне къмитите, които не касаят тази директория. Смяна на имейл адрес глобално Друга възможна ситуация е да сте забравили да пуснете git config за да настроите вашето име и имейл адрес преди да започнете същинската работа. Или пък, решавате даден проект от вашата компания да стане с отворен код и искате да смените служебните имейл адреси с персоналния ви такъв. Инструментът filter-branch може да помогне в автоматичната смяна на информацията в множество къмити. Трябва да внимавате и да смените само вашите адреси, така че използвайте --commit-filter : $ git filter-branch --commit-filter ' if [ "$GIT_AUTHOR_EMAIL" = "schacon@localhost" ]; then GIT_AUTHOR_NAME="Scott Chacon"; GIT_AUTHOR_EMAIL="schacon@example.com"; git commit-tree "$@"; else git commit-tree "$@"; fi' HEAD Тази сложничка за изписване команда ще препише всеки къмит с новия адрес, който посочите. Понеже къмитите съдържат SHA-1 данни на своите родители, това също означава, че командата ще смени хешовете на всички къмити в историята, включително и на тези, които не съдържат вашия имейл. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/ko/itsm/service-request-management/it-metrics-and-reporting | IT 메트릭: 4가지 모범 사례 | Atlassian | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 제품 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 모든 앱 보기 추천 추천 앱 Jira 유연한 프로젝트 관리 Confluence 공동 작업 중심의 지식 작업 영역 Jira Service Management 빠른 속도의 서비스 제공 Atlassian Collection 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align 신속한 서비스 제공 Jira Service Management • Customer Service Management • 자산 • Rovo 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass 제공: Rovo 팀의 지식으로 구동되는 AI 기반 앱. 개발자 Jira 유연한 프로젝트 관리 Compass 팀을 위한 소프트웨어 카탈로그 파이프라인 확장 가능한 CI/CD 자동화 Bitbucket 소스 코드 및 CI/CD DX (인수 보류 중) 생산성 및 AI 영향 측정 Rovo Dev 개발자를 위한 에이전틱 AI 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo 팀의 지식으로 구동되는 AI 기반 앱. 제품 매니저 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Jira Product Discovery 신규 아이디어 캡처 및 우선 순위 지정 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. IT 전문가 Jira Service Management 빠른 속도의 서비스 제공 Guard 신규 향상된 클라우드 보안 Rovo 팀의 지식으로 구동되는 AI 기반 앱. 비즈니스 팀 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Trello 체계적이고 시각화된 작업 Loom 신규 빠른 비동기식 동영상 업데이트 Jira Service Management 빠른 속도의 서비스 제공 Customer Service Management Customer experiences reimagined 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. 리더십 팀 Focus 신규 엔터프라이즈급 전략 계획 Talent 신규 지식 인력 계획 Jira Align 엔터프라이즈 전체에 걸친 작업 계획 및 가치 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back 솔루션 솔루션 사용 사례별 팀 협업 전략 및 계획 서비스 매니지먼트 소프트웨어 개발 팀별 소프트웨어 마케팅 IT 크기별 Enterprise 소규모 비즈니스 Startup 비영리 기관 업계별 리테일 통신 프로페셔널 서비스 정부 Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back Atlassian을 선택하는 이유 Atlassian을 선택하는 이유 업무 시스템 신규 팀 협업 방식에 대한 Atlassian의 블루프린트 통합 수천 개의 앱을 Atlassian 제품에 연결 고객 팀워크 기반의 사례 연구 및 스토리 FedRAMP 공공 부문을 위한 규정 준수 솔루션 복원력 엔터프라이즈급 및 고성능 인프라 플랫폼 고도로 통합되고 신뢰할 수 있는 안전한 플랫폼 Trust Center 데이터의 보안, 컴플라이언스 및 가용성 보장 Back 리소스 리소스 고객 지원 질문하고 버그를 신고하고 피드백을 제공 파트너 찾기 컨설팅, 교육 및 제품 사용자 지정 지원 Atlassian Ascend 전환을 위한 리소스 및 지원 커뮤니티 Atlassian 커뮤니티와 함께 배우고 소통하며 성장하세요 지원 일반적인 질문 제품 조언 파트너 지원 Enterprise 지원 기술 지원 가격 및 청구 개발자 지원 구매 및 라이선싱 리소스 프로젝트 관리 애자일 Atlassian Learning 시작하기 프로젝트 협업 팀 플레이북 제품 문서 Back Enterprise 자세한 내용 + 간략히 보기 - 무료로 시작 Jira 유연한 프로젝트 관리 Jira Service Management 빠른 속도의 서비스 제공 Confluence 모두 한곳에 있는 지식 제품 모두 보기 무료로 시작 Back 무료로 시작 ITSM Open and close the navigation menu 리소스 Jira Service Management 인시던트 관리 제품 가이드 리소스 라이브러리 IT 운영, 개발 및 비즈니스 팀을 위한 서비스 관리 규모에 맞게 빠른 속도로 서비스 관리를 지원합니다. 무료로 시작 자세히 알아보기 인시던트에 대응하고, 인시던트를 해결하며, 인시던트로부터 배우는 방법 서비스를 운영 상태로 복원하기 위한 Atlassian의 팁을 참조하세요. 자세히 알아보기 JSM을 설정하기 위해 알아야 할 모든 사항 이 가이드는 기본 정보부터 심층적인 모범 사례까지 모든 내용을 다루고 있습니다. 가이드 보기 Jira Service Management 리소스 라이브러리 백서, 사례 연구, 보고서 등을 살펴보고 필요한 모든 정보를 얻으세요. 라이브러리 보기 무료로 시작 리소스 Jira Service Management 인시던트 관리 제품 가이드 리소스 라이브러리 IT 운영, 개발 및 비즈니스 팀을 위한 서비스 관리 규모에 맞게 빠른 속도로 서비스 관리를 지원합니다. 무료로 시작 자세히 알아보기 인시던트에 대응하고, 인시던트를 해결하며, 인시던트로부터 배우는 방법 서비스를 운영 상태로 복원하기 위한 Atlassian의 팁을 참조하세요. 자세히 알아보기 JSM을 설정하기 위해 알아야 할 모든 사항 이 가이드는 기본 정보부터 심층적인 모범 사례까지 모든 내용을 다루고 있습니다. 가이드 보기 Jira Service Management 리소스 라이브러리 백서, 사례 연구, 보고서 등을 살펴보고 필요한 모든 정보를 얻으세요. 라이브러리 보기 IT 지원이란? 무료로 시작 자세히 알아보기 서비스 요청 관리 개요 서비스 데스크 구축을 위한 모범 사례 IT 메트릭 및 보고 SLA: 정의, 이유 및 방법 FCR(First Call Resolution)이 중요한 이유 지원 센터 서비스 데스크, 지원 센터 및 ITSM 비교 IT 지원을 DevOps 방식으로 실행하는 방법 대화형 티켓팅 Jira Service Management 사용자 지정 이메일 지원에서 전환 서비스 카탈로그 가상 에이전트란? IT 지원 IT 서비스 포털 IT 티켓 시스템 IT 자산 관리 개요 구성 관리 데이터베이스 구성 및 자산 관리 비교 IT 및 소프트웨어 자산 관리 모범 사례 자산 추적 하드웨어 자산 관리 자산 관리 수명 주기 인시던트 관리 개요 IT 서비스 연속성 관리 인시던트 커뮤니케이션 템플릿 워크숍 인시던트 대응 모범 사례 인시던트 관제자 항공 역할 및 책임 수명 주기 플레이북 IT 지원 수준 대기 중 담당자 대기 일정 대기 근무 급여 알림 피로 대기 근무 개선 IT 알림 에스컬레이션 정책 도구 위기 관리 템플릿 에스컬레이션 경로 템플릿 KPI 일반 메트릭 심각도 수준 가동 중지 시간으로 인한 비용 SLA, SLO, SLI 비교 오류 예산 신뢰성 및 가용성 비교 MTTF(평균 장애 시간) DevOps SRE 직접 구축하고 직접 운영 문제 관리와 인시던트 관리 비교 ChatOps ITSM 주요 인시던트 관리 IT 인시던트 관리 IT 운영을 위한 최신 인시던트 관리 IT 재해 복구 계획을 개발하는 방법 재해 복구 계획 예시 버그 추적 모범 사례 사후 검토 템플릿 비난 배제 보고서 미팅 타임라인 5개 이유 공개 및 비공개 비교 튜토리얼 인시던트 커뮤니케이션 대기 중 담당자 일정 고객 알림 자동화 핸드북 인시던트 대응 사후 검토 템플릿 생성기 용어집 핸드북 받기 2020년도 인시던트 관리 현황 2021년 인시던트 관리 현황 IT 관리 개요 문제 관리 개요 템플릿 역할 및 책임 프로세스 변경 관리 개요 모범 사례 역할 및 책임 변경 자문 위원회 변경 관리 유형 변경 관리 프로세스 지식 관리 개요 기술 자료의 정의 지식 중심 서비스(KCS)란 무엇입니까 셀프 서비스 기술 자료 엔터프라이즈 서비스 관리 개요 HR 서비스 관리 및 제공 HR 자동화 모범 사례 ESM에 대한 세 가지 구현 팁 오프보딩 프로세스 이해 직원 경험 관리 전략 최고의 온보딩 소프트웨어 9가지 직원 경험 플랫폼 온보딩 워크플로 직원 온보딩 체크리스트 IT 서비스 제공 HR 헬프 데스크 소프트웨어 HR 서비스 센터 HR 케이스 관리 변경 관리 도구 HR 자동화 HR 프로세스 개선 데이터 거버넌스 HR 서비스 제공 모델 HR 지식 관리 HR 워크플로 자동화 ITIL 개요 DevOps 및 ITIL 비교 ITIL 서비스 전략 가이드 ITIL 서비스 전환 지속적인 서비스 개선 IT 운영 개요 IT 인프라 관리 네트워크 인프라 IT 운영 관리 개요 시스템 업그레이드 서비스 매핑 애플리케이션 종속성 매핑 IT 인프라 IT 메트릭: 성공을 위한 4가지 모범 사례 IT 팀에서 측정 및 보고는 매우 중요합니다. 그러나 가능한 모든 통계를 추적하기 위해 노력하는 과정에서 IT 팀은 집중력을 잃는 경우가 있습니다. 수많은 가능성이 있기 때문에, IT 효율성을 측정하는 데 가장 적합한 IT 메트릭을 파악하기란 어려울 수 있습니다. 오늘은 IT 성과를 측정 및 보고하고 처음부터 올바른 목표를 설정하기 위한 네 가지 실용적인 가이드라인을 살펴보겠습니다. IT 메트릭이란 무엇입니까? 시작하기 전에 먼저 IT 메트릭을 정의하는 것이 좋으며, 그 목적을 이해하면 어떤 메트릭을 추적할지 결정하는 데 도움이 됩니다. IT 메트릭이란 무엇일까요? IT 메트릭은 IT 리더가 IT 비즈니스를 관리하는 데 사용하는 정량화 가능한 측정값입니다. CIO 또는 IT 책임자가 기술의 가치를 이해하고 나머지 비즈니스에 IT 팀의 가치를 입증하는 데 도움이 됩니다. 일반적인 IT 메트릭 IT의 가치를 입증하는 데 메트릭이 가진 중요성을 감안할 때, 추적할 올바른 메트릭을 선택하는 것이 핵심입니다. 가장 좋은 하나의 메트릭이란 없으며, 적합한 메트릭은 주로 IT 팀과 비즈니스에 따라 달라집니다. 이를 염두에 두고 다음과 같이 일반적으로 사용되는 몇 가지 메트릭을 살펴보겠습니다. MTTR: MTTR에 대해 이야기할 때 MTTR이 하나의 의미를 가진 단일 메트릭이라고 가정하기 쉽습니다. 하지만 사실 MTTR은 잠재적으로 네 가지 다른 측정값을 나타낼 수 있습니다. R은 해결(Resolve), 응답(Respond), 수리(Repair) 또는 복구(Recovery)를 의미할 수 있으며, 이 네 가지 메트릭은 겹치기도 하지만 저마다의 의미와 미묘한 차이가 있습니다. MTTR 메트릭에 대한 자세한 내용은 여기 에서 확인할 수 있습니다. 여기서는 세 가지 부분에 초점을 맞출 것입니다. 평균 해결 시간: 이 메트릭은 티켓이 열린 시점부터 티켓이 닫힐 때까지(그리고 이슈가 해결될 때까지)의 평균 경과 시간을 추적합니다. 평균 응답 시간: 평균 응답 시간을 통해 IT 팀은 새로 열린 티켓에 대한 평균 응답 시간을 추적할 수 있습니다. 평균 복구(또는 해결) 시간: 문제를 감지, 완화 및 해결하는 데 걸리는 시간입니다. DORA(DevOps 연구 및 평가) 연구 프로그램에 나온 바와 같이, DevOps 팀의 안정성을 측정하기 때문에 주요 DevOps 메트릭 에 해당합니다. 가동 시간: 시스템을 사용할 수 있고 가동되는 시간(백분율로 표시)입니다. 티켓당 비용: 이 메트릭은 서비스 데스크의 운영 비용을 티켓 수량으로 나누어 계산합니다. 서비스 데스크의 효율성을 파악하도록 해주며 고객 만족도와 연관시킬 수 있습니다. 고객 만족도: 고객 만족도를 측정하면 고객을 더 잘 이해하고 고객 경험을 개선하는 데 도움이 될 수 있습니다. SLA(서비스 수준 계약) : SLA는 귀하와 고객 간의(즉, IT 부서와 비즈니스 간) 일반 언어 계약으로, 여기에 언급된 하나 이상의 다른 메트릭을 포함할 수 있습니다. SLA에서 한 약속(가동 시간, 평균 해결 시간 등)은 IT 팀이 이러한 메트릭을 추적해야 하는 이유 중 하나입니다. IT 팀은 충족되는 SLA의 비율을 추적할 수 있습니다. 이러한 메트릭은 시작점을 나타낼 뿐이며, 소수의 메트릭 또는 많은 메트릭을 추적하도록 선택할 수 있습니다. 기억해야 할 중요한 점은, 팀마다 추적 및 보고의 요구 사항이 다르다는 것입니다. 다음은 인시던트 관리와 관련된 메트릭 및 KPI 에 대한 심층적인 분석입니다. 성공적인 IT 메트릭 및 보고를 위한 모범 사례 IT 메트릭의 경우 옵션이 너무 많기 때문에 어떤 항목을 추적할지 결정하기가 어렵습니다. 선택한 후에는 이러한 메트릭을 이해 관계자에게 어떻게 보고할지 생각해 보는 것도 중요합니다. IT 메트릭을 선택하고 보고하는 데 도움이 되는 몇 가지 모범 사례는 아래에 요약되어 있습니다. 비즈니스 목표에 맞게 IT 성과 목표 정렬 어떤 IT 메트릭을 추적할지 결정할 때는 IT 부서와 비즈니스에 미치는 영향을 신중하게 고려해야 합니다. 예를 들어 평균 해결 시간 및 열린 티켓의 비율 은 IT 팀이 추적하기에 유용한 메트릭이 분명하지만, 이러한 메트릭에 과도하게 의존하면 팀에 달갑지 않은 결과가 발생할 수 있습니다. 첫 번째 수준의 지원 팀이 티켓을 신속하게 닫도록 동기를 부여하면 고객의 이슈를 만족스럽게 해결하지 못한 채 티켓을 닫게 될 수 있습니다. 하위 수준의 지원 팀이 티켓을 빠르게 닫거나 에스컬레이션하도록 장려하면 실제로 회사에 더 많은 비용이 들 수 있으며 HDI에서는 수치를 통해 이를 입증할 수 있습니다. 조직에서 이러한 함정을 피하기 위해, 회사 및 조직 차원의 목표와 일맥상통하는 행동을 장려하는 의미 있는 목표와 측정값을 설정하는 방법을 모색하세요. 다양한 이해 관계자와 여러 메트릭 공유 이미 알고 있듯이, IT 메트릭은 조직의 나머지 부서에 IT 팀의 가치를 입증할 수 있는 좋은 방법입니다. 하지만 이 정보를 다른 사람들과 공유할 때는 대상 그룹을 고려하고, 해당 그룹이 어떤 정보를 보고 싶어 할지 생각해 보세요. 당연한 것이지만, 이해 관계자마다 서로 다른 것에 관심이 있습니다. 일선 IT 관리자는 기술 성능 데이터에 대해 깊은 관심을 갖는 반면 CTO는 전체적인 그림에 훨씬 더 큰 관심을 가질 수 있습니다. 모든 내용이 담긴 일반적인 보고서를 대규모의 대상에게 배포하는 대신, 주요 이해 관계자와의 회의를 통해 목표 달성에 도움이 되는 올바른 측정에 대해 합의를 이루세요. 시각적 자료를 사용하여 쉽게 이해할 수 있는 보고서 만들기 원시 데이터로 가득 찬 Excel 스프레드시트는 조회자가 데이터를 해석해야 하기 때문에 팀원, 동료 및 경영진에 대한 보고서로 사용하기에 그다지 효과적이지 않습니다. 다행히도, 이미 강력한 보고 대시보드를 사용하고 있다면 데이터에 컨텍스트를 추가하는 일은 항상 어렵지만은 않습니다. 목표, 벤치마크 및 기록과 비교하여 현재 성과를 빠르게 알리는 데 충분한 컨텍스트를 제공하는, 깔끔하고 명확하며 이해하기 쉬운 보고서를 제공해야 합니다. Atlassian의 서비스 관리 솔루션인 Jira Service Management 는 일반적인 서비스 메트릭 기능에 최적화된 기본 대시보드를 갖추고 있습니다. 보고 사항이 기본 보고서의 범위를 초과해야 하는 경우, 사용자는 전체 컨텍스트 범위를 캡처하도록 새 보고서를 편집하고 만들 수 있습니다. 추세 보고서는 일정 기간 동안의 성과를 비교하고 더 자세히 살펴볼 가치가 있는 이상 항목을 찾아볼 수 있기 때문에 특히 유용할 수 있습니다. 매달 문제 해결 시간 데이터를 살펴볼 때 다른 데이터와 비교를 하지 않았다면 7월과 8월에 열린 이슈의 개수가 크게 증가했다는 점을 눈치챌 수 없을 것입니다. 보고서를 공유하고 결과를 논의하기 전에, 전체적인 그림을 보고 데이터(가능한 경우 그 원인)를 이해하는 것이 중요합니다. 성과 기록표 작성 성과 기록표는 팀의 성과를 간단하고 개략적으로 평가하고 전달할 수 있는 방법입니다. 효과적인 성과 기록표에는 스스로에게 점수를 매기는 목표 또는 측정값, 그리고 현재 진행률을 나타내는 간편한 "신호등" 시스템(빨간색(위험), 노란색(주의) 또는 녹색(양호))이 포함됩니다. 성과 기록표에서 가장 중요한 것은 솔직함입니다. 모든 것을 항상 완벽하게 처리하는 사람은 없기 때문에 보고할 때마다 모든 범주에 스스로에게 녹색 웃는 표정을 주면 칭찬보다는 경고와 불신이 더 많이 생길 수 있습니다. 또한 실제로 문제가 발생했을 때, 성과를 솔직하게 평가하고 위험에 처한 영역에 플래그를 지정해야 지원과 이해를 받을 가능성이 더 높습니다. 운영 성과에 대한 기본 성과 기록표는 이해 관계자가 불필요한 기술 데이터에 파묻히지 않도록 하면서 신속하게 업데이트를 제공할 수 있는 좋은 방법입니다. 균형 잡힌 성과 기록표와 같은 고급 성과 기록표는 더 큰 비즈니스 목표에 대한 IT 팀의 기여도를 측정하고 전체 조직과 회사의 성과를 효과적으로 추적할 수 있습니다. 요약 위의 내용은 무엇을 어떻게 보고할지 범위를 좁히는 데 도움이 되는 기본 원칙입니다. 메트릭을 조직의 고유한 목표에 맞게 정렬하는 것이 중요합니다. Jira Service Management에서 강력한 보고 기능과 동적 차트를 통해 팀이 주요 메트릭에 대한 컨텍스트를 얻고 고객 서비스 목표를 완벽하게 파악하도록 지원하는 방법을 알아보세요. Jira Service Management 사용해 보기 문서 인시던트 관리 KPI 및 메트릭을 선택하는 방법 인시던트 관리 프로그램을 추적하려면 어떤 메트릭 및 KPI를 사용해야 합니까? 다음은 가장 일반적인 옵션과 사용 시기에 대한 가이드입니다. 게시물 읽기 다음 단계 서비스 수준 계약: 템플릿 및 모범 사례 SLA(서비스 수준 계약)는 서비스 공급자와 고객 간의 기대치를 간략하게 설명합니다. SLA를 설정하고 성과를 측정하는 방법 등의 내용을 알아보세요. 이 문서 읽기 Up Next SLAs: The What, the Why, the How 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://support.microsoft.com/hu-hu/microsoft-store-and-billing | Microsoft Store és számlázás – súgó Ugrás a tartalomtörzsre Microsoft Terméktámogatás Terméktámogatás Terméktámogatás Kezdőlap Microsoft 365 Office Termékek Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows egyebek ... Eszközök Surface PC-tartozékok Xbox PC-s játékok HoloLens Surface Hub Hardvergaranciák Fiók & számlázás Fiók Microsoft Store és számlázás Források Újdonságok Forumi zajednice Microsoft 365 rendszergazdák Kisvállalati portál Fejlesztő Oktatás Támogatási csalás bejelentése Termékbiztonság Több A Microsoft 365 megvásárlása Minden ami Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Támogatás Szoftverek Szoftverek Windows-alkalmazások Mesterséges intelligencia OneDrive Outlook Áttérés a Skype-ról a Teamsre OneNote Microsoft Teams Számítógépek és eszközök Számítógépek és eszközök Xbox vásárlása Tartozékok Szórakozás Szórakozás Xbox Game Pass Ultimate Xbox és játékok PC játékok Üzlet Üzlet Microsoft-biztonság Azure Dynamics 365 Microsoft 365 vállalatok számára Microsoft Ipar Microsoft Power Platform Windows 365 Fejlesztők és IT Fejlesztők és IT Microsoft-fejlesztő Microsoft Learn AI piactéri alkalmazások támogatása Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Egyéb Egyéb Díjmentes letöltések és biztonság Oktatás Ajándékkártyák Oldaltérkép megtekintése Keresés Segítség keresése Nincs találat Mégse Bejelentkezés Bejelentkezés Microsoft-fiókkal Jelentkezzen be, vagy hozzon létre egy fiókot. Üdvözöljük! Válasszon másik fiókot. Több fiókja van Válassza ki a bejelentkezéshez használni kívánt fiókot. Microsoft Store és számlázás – súgó Előfizetések kezelése & visszatérítéseket ad vissza Fizetési lehetőségek Korábbi rendelések Ajándékkártyák A Microsoft 365 telepítése Microsoft Store Windows rendszeren A Microsoft Store szolgáltatásainak felfedezése Az ingyenes szállítástól és a 60 napos árvédelemhez való visszatéréstől kezdve segítünk önnek a kategóriájában legjobb eszközökkel, szoftverekkel, játékokkal és erőforrásokkal kapcsolatos további műveletekben. Tekintse meg a Microsoft Store kínálatát: Vásárlással és vásárlással kapcsolatos támogatás | Termék beállítása és betanítása | Kisvállalati támogatás Vásárlással és vásárlással kapcsolatos támogatás A Microsoft Store szolgáltatásai nem minden régióban érhetők el. Az ön számára elérhető lehetőségek megtekintéséhez válassza ki az országát vagy régióját az alábbi legördülő listából, és ha nem szerepel a listán, válassza a Egyéb régiók . Régió kiválasztása Amerikai Egyesült Államok Ausztrália Kanada (angol) Kanada (francia) Egyesült Királyság Egyéb régiók Miért érdemes a Microsoft Store-ban vásárolni? Egyszerű, kényelmes vásárlás Ingyenes 2-3 napos szállítás Ingyenes 60 napos visszatérések 60 napos árvédelem Rugalmas fizetési lehetőségek Készpénz a használt eszközért Becserélés és újrahasznosítás Különleges kedvezmények és ajánlatok Diákoknak, szülőknek és oktatóknak Katonai személyzet számára Kiterjesztett eszközvédelem Microsoft Complete védelmi csomag Segítünk megtalálni, amire szüksége van Értékesítéshez kapcsolódó támogatás Fogyatékkal élőknek szóló answer desk Vásárlás ASL-munkatárssal Miért érdemes a Microsoft Store-ban vásárolni? Egyszerű, kényelmes vásárlás Ingyenes szállítás Ingyenes 60 napos visszatérések 60 napos árvédelem Készpénz a használt eszközért Becserélés és újrahasznosítás Különleges kedvezmények és ajánlatok Diákoknak, szülőknek és oktatóknak Segítünk megtalálni, amire szüksége van Értékesítéshez kapcsolódó támogatás Fogyatékkal élőknek szóló answer desk Miért érdemes a Microsoft Store-ban vásárolni? Egyszerű, kényelmes vásárlás Ingyenes szállítás Ingyenes 60 napos visszatérések 60 napos árvédelem Készpénz a használt eszközért Becserélés és újrahasznosítás Különleges kedvezmények és ajánlatok Diákoknak, szülőknek és oktatóknak Kiterjesztett eszközvédelem Microsoft Complete védelmi csomag Segítünk megtalálni, amire szüksége van Ha vásárlás előtt kérdése van, csevegjen egy termékszakértővel, vagy foglaljon le egy vásárlási találkozót. Értékesítéshez kapcsolódó támogatás Miért érdemes a Microsoft Store-ban vásárolni? Egyszerű, kényelmes vásárlás Ingyenes szállítás Ingyenes 60 napos visszatérések 60 napos árvédelem Készpénz a használt eszközért Becserélés és újrahasznosítás Különleges kedvezmények és ajánlatok Diákoknak, szülőknek és oktatóknak Kiterjesztett eszközvédelem Microsoft Complete védelmi csomag Miért érdemes a Microsoft Store-ban vásárolni? Egyszerű, kényelmes vásárlás Ingyenes szállítás Ingyenes 60 napos visszatérések 60 napos árvédelem Készpénz a használt eszközért Becserélés és újrahasznosítás Különleges kedvezmények és ajánlatok Diákoknak, szülőknek és oktatóknak Segítünk megtalálni, amire szüksége van Értékesítéshez kapcsolódó támogatás Fogyatékkal élőknek szóló answer desk Miért érdemes a Microsoft Store-ban vásárolni? Segítünk megtalálni, amire szüksége van Ha a vásárlás előtt kérdései vannak, csevegjen egy termékszakértővel. Értékesítéshez kapcsolódó támogatás Tallózás a Microsoft Store-ban A Microsoft Store Termék beállítása és betanítása Az itt felsorolt Microsoft Store-szolgáltatások közül nem minden érhető el minden régióban. A lehetőségek megtekintéséhez válassza ki az országát vagy régióját az alábbi legördülő listából: Régió kiválasztása Amerikai Egyesült Államok Ausztrália Kanada (angol) Kanada (francia) Egyesült Királyság Egyéb régiók Súgó és tanulási források Tekintse meg terméktámogatási forrásanyagainkat, amelyek segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Súgó és tanulási források Terméktámogatási forrásaink segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Súgó és tanulási források Tekintse meg terméktámogatási forrásanyagainkat, amelyek segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Súgó és tanulási források Tekintse meg terméktámogatási forrásanyagainkat, amelyek segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Súgó és tanulási források Tekintse meg terméktámogatási forrásanyagainkat, amelyek segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Súgó és tanulási források Tekintse meg terméktámogatási forrásanyagainkat, amelyek segítenek megtalálni a szükséges válaszokat. Surface-eszközök | Xbox Microsoft 365 | Windows Kisvállalati támogatás A régióban elérhető kisvállalati támogatási lehetőségek megtekintéséhez válassza ki az országát vagy régióját az alábbi legördülő listából: Régió kiválasztása Amerikai Egyesült Államok Ausztrália Kanada (angol) Kanada (francia) Egyesült Királyság Egyéb régiók Források a kisvállalat számára Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és tanulás Kisvállalati erőforrásközpont Források a kisvállalat számára Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és tanulás Kisvállalati erőforrásközpont Források a kisvállalat számára Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és tanulás Kisvállalati erőforrásközpont Források a kisvállalat számára Az üzleti igények felmérésétől a beállítás és a hibaelhárítás támogatásán át a segítségére vagyunk. Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és képzés Kisvállalati erőforrásközpont Források a kisvállalat számára Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és tanulás Kisvállalati erőforrásközpont Források a kisvállalat számára Tanácsokat, ingyenes képzéseket, termékeket és eszközöket kaphat a vállalkozása gyarapodásához. Kisvállalati súgó és tanulás Újdonságok Copilot szervezeteknek Copilot személyes használatra Microsoft 365 Fedezze fel a Microsoft termékeit Windows 11-alkalmazások Microsoft Store Fiókprofil Letöltőközpont Microsoft Store-támogatás Visszaküldés Rendeléskövetés Újrahasznosítás Commercial Warranties Oktatás Microsoft Education Oktatási eszközök Microsoft Teams oktatáshoz Microsoft 365 Education Office oktatási verzió Oktatóképzés és -fejlesztés Ajánlatok diákoknak és szülőknek Azure diákoknak Üzlet Microsoft-biztonság Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamshez készült Fejlesztők és IT Microsoft-fejlesztő Microsoft Learn AI piactéri alkalmazások támogatása Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Vállalat Karrier A Microsoft bemutatása Vállalati hírek Adatvédelem a Microsoftnál Befektetők Korrupció- és Vesztegetésellenes Elkötelezettségünk Fenntarthatóság Magyar (Magyarország) Adatvédelmi beállítások elutasítása ikon Adatvédelemmel kapcsolatos választási lehetőségek Adatvédelmi beállítások elutasítása ikon Adatvédelemmel kapcsolatos választási lehetőségek Fogyasztói állapot adatainak védelme Kapcsolatfelvétel a Microsofttal Adatvédelem Cookie-k kezelése Használati feltételek Védjegyek A hirdetéseinkről EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/GitHub-%d0%a1%d1%8a%d0%b7%d0%b4%d0%b0%d0%b2%d0%b0%d0%bd%d0%b5-%d0%b8-%d0%bd%d0%b0%d1%81%d1%82%d1%80%d0%be%d0%b9%d0%ba%d0%b0-%d0%bd%d0%b0-%d0%b0%d0%ba%d0%b0%d1%83%d0%bd%d1%82 | Git - Създаване и настройка на акаунт About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 4.1 GitHub - Създаване и настройка на акаунт GitHub е най-голямата онлайн услуга за съхранение на Git хранилища и централна точка за съвместна работа на милиони разработчици и проекти. Голям процент от всички Git хранилища се хостват в GitHub и много проекти с отворен код ползват платформата като средство за проследяване на проблеми, преглед на код и много други неща. Въпреки, че GitHub не е директно свързан със самия Git като проект с отворен код, доста вероятно е да искате или да трябва да комуникирате с GitHub в определени моменти от професионалната ви работа. Тази глава е посветена на това как да използваме ефективно GitHub. Ще разгледаме създаването и управлението на акаунт, създаване и ползване на Git хранилища, популярните методи за сътрудничество в проекти, за приемане на външна помощ във ваши проекти, програмният интерфейс на GitHub и много други малки трикове, които да ви улеснят работата. Ако за вас GitHub не представлява интерес, можете спокойно да пропуснете тази глава и да преминете към Git инструменти . Създаване и настройка на акаунт Първото нещо, което трябва да сторите, е да си създадете безплатен акаунт. Просто отворете https://github.com , изберете си незаето потребителско име, посочете имейл адрес и парола и натиснете големия зелен бутон “Sign up for GitHub”. Фигура 81. Регистрационната форма на GitHub Следващото нещо, което ще видите, е страницата с платени планове - засега можете да я игнорирате. GitHub ще ви изпрати имейл за потвърждение на подадения адрес. Продължете и направете това, доста е важно (както ще видите по-късно). Забележка GitHub предоставя почти всичките си функции безплатно, с изключение на някои по-модерни екстри. Платените планове на GitHub включват по-модерни инструменти и функции, както и увеличени лимити за безплатните услуги, но ние няма да се занимаваме с тях в тази книга. Повече информация за наличните планове и сравнения между плановете може да намерите на https://github.com/pricing . Щраквайки върху Octocat логото в горния ляв ъгъл на екрана, ще попаднете във вашата dashboard страница. Вече можете да ползвате GitHub. SSH достъп В този момент, можете да се свързвате с хранилищата си по HTTPS с името и паролата, които създадохте при регистрацията. Обаче, за просто клониране на публични проекти, те не са ви нужни - акаунтът, който създадохте влиза в действие когато правите огледални копия на хранилища (fork) и изпращате промени към тези копия по-късно. Ако искате да използвате SSH отдалечени хранилища, ще трябва да конфигурирате публичен ключ. Ако още нямате такъв, погледнете [_generate_ssh_key] . Отворете настройките на акаунта през линка в горната дясна част на прозореца: Фигура 82. “Account settings” линк След това, изберете “SSH keys” секцията отляво. Фигура 83. “SSH keys” линк Оттук, натиснете бутона “Add an SSH key”, дайте описателно име на ключа, вмъкнете съдържанието на файла ви ~/.ssh/id_rsa.pub (или както сте го кръстили) в text area полето и натиснете “Add key”. Забележка Дайте име на SSH ключ, което се помни. Можете да използвате имена като "My Laptop" или "Work Account", така че ако искате по-късно да изтриете даден ключ, да можете лесно да разберете кой е той всъщност. Вашият аватар След това, ако желаете, можете да замените генерирания автоматично аватар с изображение по ваш вкус. Отворете секцията “Profile” (над SSH Keys) и натиснете “Upload new picture”. Фигура 84. “Profile” линк Ние сме избрали копие на Git логото на нашия диск и след това получаваме възможност да го изрежем. Фигура 85. Изрязване на аватара Сега всеки път, когато правите нещо в сайта, другите ще виждат аватара ви до потребителското име. Ако сте качили аватар в популярната услуга Gravatar (често ползвана за Wordpress акаунти), то той ще бъде използван по подразбиране и няма нужда да минавате през тази стъпка. Вашите имейл адреси GitHub използва имейл адреса, за да асоциира Git къмитите с вашия потребител. Ако използвате няколко адреса във вашите къмити и искате GitHub да ги свързва правилно, ще трябва да ги добавите всичките в Emails секцията на административния интерфейс. Фигура 86. Добавяне на имейл адреси В Добавяне на имейл адреси можем да видим някои от различните възможни статуси. Най-горният адрес се верифицира и определя като основен такъв, което значи че ще бъде използван за получаване на нотификации. Вторият адрес също се верифицира и може да бъде използван за основен, ако желаете да ги размените. Последният адрес не се верифицира и не може да се използва като основен. Ако GitHub види някой от тези адреси в къмит съобщенията в кое да е хранилище в сайта, то те ще бъдат асоциирани с вашия потребител. Двустъпкова автентикация Накрая, за допълнителна сигурност, определено е добре да настроите функцията за Two-factor Authentication или “2FA”. Двустъпковата автентикация е оторизационен механизъм, който е много популярен напоследък като средство за намаляване на риска от открадване на акаунта, в случай че някой разбере паролата ви. Включването ѝ ще укаже на GitHub да изисква два различни метода за оторизиране на достъпа, така че ако единият от тях е компрометиран, атакуващият да не може да получи достъп до акаунта ви. Можете да откриете настройките за Two-factor Authentication в секцията Security на Account settings. Фигура 87. 2FA в секцията Security Ако натиснете бутона “Set up two-factor authentication”, ще се отвори конфигурационна страница, в която можете да изберете да използвате телефонно приложение за генериране на вторичен код за достъп (“time based one-time password”), или пък можете да укажете на GitHub да ви изпраща SMS с кода всеки път, когато се логвате. След като изберете желания метод и изпълните инструкциите за настройка на 2FA, акаунтът ви ще бъде малко по-защитен и ще трябва да въведете код за достъп в допълнение към паролата си всеки път, когато се логвате в GitHub. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.notion.com/pt/integrations/asana | Integrações com Asana | Conecte seus apps com a Notion Notion Recursos IA do Notion Crie, escreva, automatize Agentes Lida com tarefas manuais Busca Enterprise Encontre respostas instantaneamente Anotações IA Redigido impecavelmente por IA Documentos Simples e eficiente Base de conhecimento Centralize seu conhecimento Projetos Gerencie qualquer projeto Sites Coloque suas ideias online Começar a usar Explore os casos de uso de IA O que a IA do Notion pode fazer Procurar no marketplace Modelos para tudo Ver integrações Conecte seus aplicativos com o Notion Baixar o Web Clipper Salve conteúdos da web no Notion Teste o aplicativo desktop e desfrute de uma experiência mais ágil Baixar aplicativo Mail Calendar IA Enterprise Preços Explorar Equipes Engenharia e Produto Design Marketing TI Tamanho da equipe Startups PMEs Grandes Empresas Educação Aprender Centro de ajuda Universidade Notion Histórias de clientes Blog Comunidade Programas de parceiros Construir API Modelos Segurança Consultores Solicite uma demonstração Fazer login Use o Notion de graça ← Integrações Asana Adicionar ao Notion Overview O Asana potencializa as empresas ao organizar o seu trabalho em um único espaço. Use a pré-visualização do link para visualizar as tarefas do Asana diretamente em uma página do Notion, ou use uma base de dados sincronizada para trazer seus projetos Asana para a base de dados do Notion – e use filtros de base de dados, visualização, rollups e relação para criar uma visualização personalizada dos seus projetos para que todos na sua equipe possam ver o status do projeto. How to use Para criar uma visualização do conteúdo do Asana no Notion , cole qualquer link do Asana no Notion e selecione Colar como visualização . Você também pode digitar /asana em qualquer página do Notion será exibido um menu, que permite que você cole os links diretamente Se for a primeira vez que estiver usando o Asana com o Notion, será solicitado que você autorize a integração. Siga as instruções para concluir o processo de autorização. Uma vez autorizado, você verá uma visualização detalhada do conteúdo vinculado Para sincronizar os dados do Asana em uma base de dados do Notion , copie um link do Asana em um projeto ou tarefa, cole o link no Notion e selecione Colar como base de dados . Uma base de dados do Notion com propriedades do Asana será exibida e a tarefa começará a ser preenchida automaticamente Tenha em mente que esta não é uma sincronização bidirecional. Os seus dados serão duplicados no Notion no momento da importação e nenhuma alteração será sincronizada. Saiba mais sobre as bases de dados sincronizadas do Notion Para importar os seus dados do Asana para o Notion , siga este guia Feito por Notion Categoria Produtividade Colaboração Recursos Prévia do link Base de dados sincronizada Links do desenvolvedor Site Termos / Privacidade Suporte por e-mail Reportar um problema Todas as marcas registradas de terceiros (incluindo logotipos e ícones) aqui mencionadas são propriedade de seus respectivos titulares. Exceto se especificamente designadas como "Criada pelo Notion", as integrações não têm suporte e nem são mantidas pelo Notion. Os produtos ou serviços de terceiros aos quais as Integrações se conectam são Aplicativos de Terceiros (conforme definido no Contrato de Assinatura Mestre ou Termos de Uso Pessoal , conforme aplicável). Ao habilitar qualquer integração ou usar a Galeria de Integrações do Notion, você concorda com os Termos da Galeria de Integrações . Mais integrações PortalWith Create Client Portal with Notion STR Desk Sync Vacation Rental data with Notion in seconds VECTOR AI Your AI Partner Emon Sync Outlook Emails to Notion Notixel Automate your data flow between Notion and Microsoft Excel. neuforms the most affordable typeform alternative to build forms Português (Brasil) Configurações de cookies © 2026 Notion Labs, Inc. Empresa Sobre nós Carreiras Segurança Status Termos e privacidade Seus direitos de privacidade Baixar iOS e Android Mac e Windows Calendário Web Clipper Recursos Centro de ajuda Preços Blog Comunidade Integrações Modelos Programas de parceiros Notion para Enterprise Pequenas empresas Individual Descubra mais → | 2026-01-13T09:29:44 |
https://git-scm.com/book/pl/v2/Rozproszony-Git-Wgrywanie-zmian-do-projektu | Git - Wgrywanie zmian do projektu About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pierwsze kroki 1.1 Wprowadzenie do kontroli wersji 1.2 Krótka historia Git 1.3 Podstawy Git 1.4 Linia poleceń 1.5 Instalacja Git 1.6 Wstępna konfiguracja Git 1.7 Uzyskiwanie pomocy 1.8 Podsumowanie 2. Podstawy Gita 2.1 Pierwsze repozytorium Gita 2.2 Rejestrowanie zmian w repozytorium 2.3 Podgląd historii rewizji 2.4 Cofanie zmian 2.5 Praca ze zdalnym repozytorium 2.6 Tagowanie 2.7 Aliasy 2.8 Podsumowanie 3. Gałęzie Gita 3.1 Czym jest gałąź 3.2 Podstawy rozgałęziania i scalania 3.3 Zarządzanie gałęziami 3.4 Sposoby pracy z gałęziami 3.5 Gałęzie zdalne 3.6 Zmiana bazy 3.7 Podsumowanie 4. Git na serwerze 4.1 Protokoły 4.2 Uruchomienie Git na serwerze 4.3 Generowanie Twojego publicznego klucza SSH 4.4 Konfigurowanie serwera 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Inne opcje hostowania przez podmioty zewnętrzne 4.10 Podsumowanie 5. Rozproszony Git 5.1 Rozproszone przepływy pracy 5.2 Wgrywanie zmian do projektu 5.3 Utrzymywanie projektu 5.4 Podsumowanie 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Narzędzia Gita 7.1 Wskazywanie rewizji 7.2 Interaktywne używanie przechowali 7.3 Schowek i czyszczenie 7.4 Signing Your Work 7.5 Searching 7.6 Przepisywanie historii 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugowanie z Gitem 7.11 Moduły zależne 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Podsumowanie 8. Dostosowywanie Gita 8.1 Konfiguracja Gita 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git i inne systemy 9.1 Git jako klient 9.2 Migracja do Gita 9.3 Podsumowanie 10. Mechanizmy wewnętrzne w Git 10.1 Komendy typu plumbing i porcelain 10.2 Obiekty Gita 10.3 Referencje w Git 10.4 Spakowane pliki (packfiles) 10.5 Refspec 10.6 Protokoły transferu 10.7 Konserwacja i odzyskiwanie danych 10.8 Environment Variables 10.9 Podsumowanie A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Rozproszony Git - Wgrywanie zmian do projektu Wgrywanie zmian do projektu Główną trudnością podczas opisywania tego procesu, jest bardzo duża różnorodność sposobów w jaki jest to realizowane. Ponieważ Git jest bardzo elastycznym narzędziem, ludzie mogą i współpracują ze sobą na różne sposoby, dlatego też trudne jest pokazanie w jaki sposób Ty powinieneś – każdy projekt jest inny. Niektóre ze zmiennych które warto wziąć pod uwagę to ilość aktywnych współpracowników, wybrany sposób przepływów pracy, uprawnienia, oraz prawdopodobnie sposób współpracy z zewnętrznymi programistami. Pierwszą zmienną jest ilość aktywnych współpracowników – ilu aktywnych współpracowników/programistów aktywnie wgrywa zmiany do projektu, oraz jak często? Najczęściej będzie to sytuacja, w której uczestniczy dwóch lub trzech programistów, wgrywających kilka razy na dzień zmiany (lub nawet mniej, przy projektach nie rozwijanych aktywnie). Dla bardzo dużych firm lub projektów, ilość programistów może wynieść nawet tysiące, z dziesiątkami lub nawet setkami zmian wgrywanych każdego dnia. Jest to bardzo ważne, ponieważ przy zwiększającej się liczbie programistów, wypływa coraz więcej problemów podczas włączania efektów ich prac. Zmiany które próbujesz wgrać, mogą stać się nieużyteczne, lub niepotrzebne ze względu na zmiany innych osób z zespołu. Tylko w jaki sposób zachować spójność kodu i poprawność wszystkich przygotowanych łatek? Następną zmienną jest sposób przepływu pracy w projekcie. Czy jest scentralizowany, w którym każdy programista ma równy dostęp do wgrywania kodu? Czy projekt posiada głównego opiekuna, lub osobę integrującą, która sprawdza wszystkie łatki? Czy wszystkie łatki są wzajemnie zatwierdzane? Czy uczestniczysz w tym procesie? Czy funkcjonuje porucznik, do którego musisz najpierw przekazać swoje zmiany? Następnym elementem są uprawnienia do repozytorium. Sposób pracy z repozytorium do którego możesz wgrywać zmiany bezpośrednio, jest zupełnie inny, od tego w którym masz dostęp tylko do odczytu. Jeżeli nie masz uprawnień do zapisu, w jaki sposób w projekcie akceptowane są zmiany? Czy ma on określoną politykę? Jak duże zmiany wgrywasz za jednym razem? Jak często je wgrywasz? Odpowiedzi na wszystkie te pytania, mogą wpływać na to w jaki sposób będziesz wgrywał zmiany do repozytorium, oraz jaki rodzaj przepływu pracy jest najlepszy lub nawet dostępny dla Ciebie. Omówimy aspekty każdej z nich w serii przypadków użycia, przechodząc od prostych do bardziej złożonych; powinieneś móc skonstruować konkretny przepływ pracy który możesz zastosować w praktyce z tych przykładów. Wskazówki wgrywania zmian Zanim spojrzysz na poszczególne przypadki użycia, najpierw szybka informacja o treści komentarzy do zmian ( commit messages ). Dobre wytyczne do tworzenia commitów, oraz związanych z nią treścią komentarzy pozwala na łatwiejszą pracę z Gitem oraz innymi współpracownikami. Projekt Git dostarcza dokumentację która pokazuje kilka dobrych rad dotyczących tworzenia commitów i łat – możesz ją znaleźć w kodzie źródłowym Gita w pliku Documentation/SubmittingPatches . Po pierwsze, nie chcesz wgrywać żadnych błędów związanych z poprawkami pustych znaków (np. spacji). Git dostarcza łatwy sposób do tego – zanim wgrasz zmiany, uruchom git diff --check , komenda ta pokaże możliwe nadmiarowe spacje. Figure 57. Wynik polecenia git diff --check . Jeżeli uruchomisz tę komendę przed commitem, dowiesz się czy zamierzasz wgrać zmiany które mogą zdenerwować innych programistów. Następnie spróbuj w każdym commit-ie zawrzeć logicznie odrębny zestaw zmian. Jeżeli możesz, twórz nie za duże łatki – nie programuj cały weekend poprawiając pięć różnych błędów, aby następnie wszystkie je wypuścić w jednym dużym commit-cie w poniedziałek. Nawet jeżeli nie zatwierdzasz zmian w ciągu weekendu, użyj przechowalni ("stage"), aby w poniedziałek rozdzielić zmiany na przynajmniej jeden commit dla każdego błędu, dodając użyteczny komentarz do każdego commitu. Jeżeli niektóre ze zmian modyfikują ten sam plik, spróbuj użyć komendy git add --patch , aby częściowo dodać zmiany do przechowalni (dokładniej opisane to jest w rozdziale Interaktywne używanie przechowali ). Końcowa migawka projektu w gałęzi jest identyczna, nieważne czy zrobisz jeden czy pięć commitów, więc spróbuj ułatwić życie swoim współpracownikom kiedy będą musieli przeglądać Twoje zmiany. Takie podejście ułatwia również pobranie lub przywrócenie pojedynczych zestawów zmian w razie potrzeby. Rozdział Przepisywanie historii opisuje kilka ciekawych trików dotyczących nadpisywania historii zmian i interaktywnego dodawania plików do przechowalni – używaj ich do utrzymania czystej i przejrzystej historii. Ostatnią rzeczą na którą należy zwrócić uwagę są komentarze do zmian. Tworzenie dobrych komentarzy pozwala na łatwiejsze używanie i współpracę za pomocą Gita. Generalną zasadą powinno być to, że treść komentarza rozpoczyna się od pojedynczej linii nie dłuższej niż 50 znaków, która zwięźle opisuje zmianę, następnie powinna znaleźć się pusta linia, a poniżej niej szczegółowy opis zmiany. Projekt Git wymaga bardzo dokładnych wyjaśnień motywujących Twoją zmianę w stosunku do poprzedniej implementacji – jest to dobra wskazówka do naśladowania. Dobrym pomysłem jest używania czasu teraźniejszego w trybie rozkazującym. Innymi słowy, używaj komend. Zakładając używanie języka angielskiego w repozytorium, zamiast "I added tests for" lub "Adding tests for", użyj "Add tests for". Poniżej znajduje się szablon komentarza przygotowany przez Tima Pope: Krótkie (50 znaków lub mniej) podsumowanie zmian. Bardziej szczegółowy tekst jeżeli jest taka konieczność. Zawijaj wiersze po około 72 znakach. Czasami pierwsza linia jest traktowana jako temat wiadomości email, a reszta komentarza jako treść. Konieczna jest pusta linia oddzielająca podsumowanie od głównej części opisu zmian (chyba że całkowicie pominiesz główną część opisu zmian); narzędzia takie jak `rebase` mogą się pogubić jeśli ich nie oddzielisz. Kolejne paragrafy następują po pustej linii. - wypunktowania są również poprawne, - zazwyczaj myślnik lub gwiazdka jest używana do punktowania, poprzedzona pojedynczym znakiem spacji, z pustą linią pomiędzy, jednak zwyczaje mogą się tutaj różnić. Jeżeli wszystkie Twoje komentarz do zmian będą wyglądały jak ten, współpraca będzie dużo łatwiejsza dla Ciebie i twoich współpracowników. Projekt Git ma poprawnie sformatowane komentarze, uruchom polecenie git log --no-merges na tym projekcie, aby zobaczyć jak wygląda ładnie sformatowana i prowadzona historia zmian. W poniższych przykładach, i przez większość tej książki, ze względu na zwięzłość nie sformatowałem treści komentarzy tak ładnie; używam opcji -m do git commit . Rób tak jak mówię, nie tak jak robię. Małe prywatne zespoły Najprostszym przykładem który możesz spotkać, to prywatne repozytorium z jednym lub dwoma innymi współpracownikami. Jako "prywatne", mamy na myśli repozytorium z zamkniętym kodem źródłowym – niedostępnym do odczytu dla innych. Ty i inny deweloperzy mają uprawniania do wgrywania ("push") swoich zmian. W takim środowisku możesz naśladować sposób pracy znany z Subversion czy innego scentralizowanego systemu kontroli wersji. Nadal masz wszystkie zalety takie jak commitowanie bez dostępu do centralnego serwera, oraz prostsze tworzenie gałęzi i łączenie zmian, ale przepływ pracy jest bardzo podobny; główną różnicą jest to, że łączenie zmian wykonywane jest po stronie klienta a nie serwera podczas commitu. Zobaczmy jak to może wyglądać, w sytuacji w której dwóch programistów rozpocznie prace z współdzielonym repozytorium. Pierwszy programista, John, klonuje repozytorium, wprowadza zmiany i zatwierdza je lokalnie. (Część komunikatów została zastąpiona znakami ... aby skrócić przykłady.) # Komputer Johna $ git clone john@githost:simplegit.git Initialized empty Git repository in /home/john/simplegit/.git/ ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'removed invalid default value' [master 738ee87] removed invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) Druga programistka, Jessica, robi to samo – klonuje repozytorium i commituje zmianę: # Komputer Jessiki $ git clone jessica@githost:simplegit.git Initialized empty Git repository in /home/jessica/simplegit/.git/ ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Następnie, Jessica wypycha swoje zmiany na serwer: # Komputer Jessiki $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master John próbuje również wypchnąć swoje zmiany: # Komputer Johna $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' John nie może wypchnąć swoich zmian, ponieważ w międzyczasie Jessica wypchnęła swoje. To jest szczególnie ważne do zrozumienia, jeżeli przywykłeś do Subversion, ponieważ zauważysz że każdy z deweloperów zmieniał inne pliki. Chociaż Subversion automatycznie połączy zmiany po stronie serwera jeżeli zmieniane były inne pliki, w Git musisz połączyć zmiany lokalnie. John musi pobrać zmiany Jessiki oraz włączyć je do swojego repozytorium zanim będzie wypychał swoje zmiany: $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master W tym momencie lokalne repozytorium Johna wygląda mniej więcej tak: Figure 58. Rozbieżna historia w repozytorium Johna. John ma już odniesienie do zmian, które wypchnęła Jessica, ale musi je lokalnie połączyć ze swoimi zmianami, zanim będzie w stanie je wypchnąć: $ git merge origin/master Merge made by recursive. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Łączenie zmian poszło bez problemów – historia zmian u Johna wygląda następująco: Figure 59. Repozytorium Johna po połączeniu z origin/master . Teraz John może przetestować swój kod tak, aby upewnić się, że nadal działa poprawnie, a następnie wypchnąć swoje zmiany na serwer: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master Ostatecznie, historia zmian u Johna wygląda tak: Figure 60. Historia zmian Johna po wypchnięciu ich na serwer origin . W tym samym czasie, Jessica pracowała na swojej tematycznej gałęzi. Stworzyła gałąź issue54 oraz wprowadziła trzy zmiany w niej. Nie pobrała jeszcze zmian Johna, więc jej historia zmian wygląda tak: Figure 61. Gałąź tematyczna Jessiki. Jessica chce zsynchronizować się ze zmianami Johna, więc je pobiera ( fetch ): # Komputer Jessiki $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master Ta komenda pobiera zmiany Johna, które wprowadził w międzyczasie. Historia zmian u Jessiki wygląda następująco: Figure 62. Historia zmian u Jessiki po pobraniu zmian Johna. Jessica uważa swoje prace w tej gałęzi za zakończone, ale chciałaby wiedzieć jakie zmiany musi włączyć aby mogła wypchnąć swoje. Uruchamia komendę git log aby się tego dowiedzieć: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 removed invalid default value Składnia issue54..origin/master jest filtrem logu, który prosi Gita o pokazanie tylko listy commitów, które są na drugiej gałęzi (w tym przypadku origin/master ), które nie są na pierwszej gałęzi (w tym przypadku issue54 ). Omówimy tę składnię szczegółowo w Zakresy zmian . Na razie widzimy w wyniku powyższego polecenia, że jest jeden commit Johna, którego nie scaliła Jessicą. Jeśli dołączy ona zmiany z origin/master , to będzie to pojedynczy commit, który zmodyfikuje jej lokalną pracę. Teraz Jessica może połączyć swoje zmiany tematyczne do swojej głównej gałęzi master , włączyć zmiany Johna ( origin/master ) do swojej gałęzi master , a następnie wypchnąć zmiany ponownie na serwer. Najpierw przełącza się z powrotem do swojej głównej gałęzi master , tak aby zintegrować całą tę pracę: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jako pierwszą gałąź może ona włączyć zarówno origin/master jak i issue54 – obie są nadrzędne więc kolejność nie ma znaczenia. Końcowa wersja plików powinna być identyczna bez względu na wybraną kolejność; tylko historia będzie się lekko różniła. Jako pierwszą gałąź do włączenia Jessica wybiera issue54 : $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) Nie było problemów; jak widzisz był to proste połączenie tzw. fast-forward . Teraz Jessica może włączyć zmiany Johna ( origin/master ): $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Wszystko połączyło się bez problemów, więc historia zmian u Jessiki wygląda następująco: Figure 63. Historia zmian u Jessiki po włączeniu zmian Johna. Teraz origin/master jest dostępny z gałęzi master u Jessiki, więc powinna bez problemów móc wypchnąć swoje zmiany (zakładając że w międzyczasie John niczego nie wypchnął): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Każdy programista wprowadził zmiany kilkukrotnie, oraz połączył zmiany drugiego bez problemów. Figure 64. Historia zmian u Jessiki po wypchnięciu zmian na serwer. Jest to jeden z najprostszych przepływów pracy. Pracujesz przez chwilę, generalnie na tematycznych gałęziach i włączasz je do gałęzi master kiedy są gotowe. Kiedy chcesz podzielić się swoją pracą, włączasz je do swojej gałęzi master , pobierasz i włączasz zmiany z origin/master jeżeli jakieś były, a następnie wypychasz gałąź master na serwer. Zazwyczaj sekwencja będzie wyglądała mniej więcej tak: Figure 65. Sekwencja zdarzeń dla prostego przepływu zmian między programistami. Prywatne zarządzane zespoły W tym scenariuszu, zobaczysz jak działa współpraca w większych prywatnych grupach. Nauczysz się jak pracować w środowisku w którym małe grupy współpracują ze sobą nad funkcjonalnościami, a następnie stworzone przez nich zmiany są integrowane przez inną osobę. Załóżmy że John i Jessica wspólnie pracują nad jedną funkcjonalnością, a Jessica i Josie nad drugą. W tej sytuacji, organizacja używa przepływu pracy z osobą integrującą zmiany, w której wyniki pracy poszczególnych grup są integrowane przez wyznaczone osoby, a gałąź master może być jedynie przez nie aktualizowana W tym scenariuszu, cała praca wykonywana jest w osobnych gałęziach zespołów, a następnie zaciągana przez osoby integrujące. Prześledźmy sposób pracy Jessiki w czasie gdy pracuje ona nad obiema funkcjonalnościami, współpracując jednocześnie z dwoma niezależnymi programistami. Zakładając że ma już sklonowane repozytorium, rozpoczyna pracę nad funkcjonalnością featureA . Tworzy dla niej nową gałąź i wprowadza w niej zmiany: # Komputer Jessiki $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) Teraz musi podzielić się swoją pracą z Johnem, więc wypycha zmiany z gałęzi featureA na serwer. Jessica nie ma uprawnień do zapisywania w gałęzi master – tylko osoby integrujące je mają – więc musi wysłać osobną gałąź aby współpracować z Johnem: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica powiadamia Johna e-mailem, że wysłała swoje zmiany w gałęzi featureA i może je on zweryfikować. W czasie gdy czeka na informację zwrotną od Johna, Jessica rozpoczyna pracę nad featureB z Josie. Na początku, tworzy nową gałąź przeznaczoną dla nowej funkcjonalności, podając jako gałąź źródłową gałąź master na serwerze: # Komputer Jessiki $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Następnie, Jessica wprowadza kilka zmian i zapisuje je w gałęzi featureB : $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Repozytorium Jessiki wygląda następująco: Figure 66. Początkowa historia zmian u Jessiki. Jest gotowa do wypchnięcia swoich zmian, ale dostaje wiadomość e-mail od Josie, że gałąź z pierwszymi zmianami została już udostępniona na serwerze jako featureBee . Jessica najpierw musi połączyć te zmiany ze swoimi, zanim będzie mogła wysłać je na serwer. Może więc pobrać zmiany Josie za pomocą komendy git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Jessica może teraz połączyć zmiany ze swoimi za pomocą git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) Powstał drobny problem – musi wysłać połączone zmiany ze swojej gałęzi featureB do featureBee na serwerze. Może to zrobić poprzez wskazanie lokalnej i zdalnej gałęzi oddzielonej dwukropkiem (:), jako parametr do komendy git push : $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee Jest to nazywane refspec . Zobacz sekcję Refspec aby dowiedzieć się więcej o refspec i o rzeczach, które można z nimi zrobić. Zwróć uwagę również na flagę -u ; jest to skrót od flagi --set-upstream , która konfiguruje gałęzie aby później łatwiej wypychało się pobierało zmiany. Następnie John wysyła e-mail do Jessiki z informacją, że wgrał swoje zmiany do gałęzi featureA i prosi ją o ich weryfikację. Uruchamia więc ona git fetch aby pobrać te zmiany: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Następnie za pomocą komendy git log może ona zobaczyć co zostało zmienione: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 Ostatecznie, integruje ona zmiany Johna ze swoimi znajdującymi się w gałęzi featureA : $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Jessica postanawia jednak jeszcze coś poprawić, więc commituje ponownie i wysyła zmiany z powrotem na serwer: $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Historia zmian u Jessiki wygląda teraz mniej więcej tak: Figure 67. Historia zmian u Jessiki po wprowadzeniu zmian w gałęzi. Jessica, Josie i John powiadamiają osoby zajmujące się integracją, że gałęzie featureA i featureBee na serwerze są gotowe do integracji z głównym kodem. Po włączeniu tych gałęzi do głównej, zostaną pobrane zmiany, tworząc historię zmian podobną do poniższej: Figure 68. Historia zmian u Jessiki po włączeniu jej obu gałęzi. Wiele osób przechodzi na Gita ze względu na możliwość jednoczesnej współpracy kilku zespołów, oraz możliwości włączania efektów ich prac w późniejszym terminie. Możliwość tworzenie małych, współpracujących ze sobą grup przy pomocy zdalnych gałęzi bez konieczności angażowania pozostałych członków zespołu, jest bardzo dużą zaletą Gita. Sekwencja przepływu pracy, którą tutaj zobaczyłeś, jest podobna do poniższej: Figure 69. Podstawowa sekwencja omawianego przepływu pracy w zespole zarządzanym. Sforkowany publiczny projekt Współpraca przy projektach publicznych jest trochę inne. Ponieważ nie masz uprawnień do bezpośredniego wgrywania zmian w projekcie, musisz przekazać swoje zmiany do opiekunów w inny sposób. Pierwszy przykład opisuje udział w projekcie poprzez rozwidlenie (fork) w serwisie, który to umożliwia. Wiele serwisów hostingowych udostępnia taką możliwość (w tym GitHub, BitBucket, Google Code, repo.or.cz i inne), a wielu opiekunów projektów oczekuje takiego stylu współpracy. Następna sekcja opisuje współpracę w projektach, które preferują otrzymywanie poprawek poprzez e-mail. Po pierwsze, na początku musisz sklonować główne repozytorium, stworzyć gałąź tematyczną dla zmian które planujesz wprowadzić oraz dokonać tam zmian. Sekwencja komend wygląda następująco: $ git clone (url) $ cd project $ git checkout -b featureA # (zmiany) $ git commit # (zmiany) $ git commit Note Możesz chcieć użyć rebase -i , aby złączyć swoje zmiany do jednego commita, lub przeorganizować je, tak aby poprawka była łatwiejsza do zweryfikowania przez opiekuna - zobacz sekcję Przepisywanie historii , aby dowiedzieć się więcej o tego typu operacjach. Kiedy zmiany w Twojej gałęzi zostaną zakończone i jesteś gotowy do przekazania ich do opiekunów projektu, wejdź na stronę projektu i kliknij przycisk "Fork", tworząc w ten sposób swoją własną kopię projektu z uprawnieniami do zapisu. Następnie musisz dodać nowy URL do repozytorium jako drugie repozytorium zdalne, w tym przypadku nazwane myfork : $ git remote add myfork (url) Musisz teraz wysłać do niego swoje zmiany. Najprościej będzie wypchnąć gałąź tematyczną, na której pracujesz, do zdalnego repozytorium, zamiast włączać zmiany do Twojej gałęzi master i dopiero potem je wysyłać. Warto zrobić tak dlatego, że w sytuacji, w której Twoje zmiany nie zostaną zaakceptowane lub zostaną zaakceptowane tylko częściowo, nie będziesz musiał cofać swojej gałęzi master . Jeżeli opiekun włączy, zmieni bazę lub pobierze część Twoich zmian, będziesz mógł je otrzymać zaciągając je z ich repozytorium: $ git push -u myfork featureA Kiedy wgrasz wprowadzone zmiany do swojego rozwidlenia projektu, powinieneś powiadomić o tym opiekuna. Jest to często nazywane operacją pull request i możesz ją wykonać albo poprzez stronę internetową – GitHub ma własny mechanizm "Pull Request", który omówimy w rodziale GitHub – albo wykonując komendę git request-pull i ręcznie wysyłając jej wynik e-mailem do opiekuna projektu. Komenda request-pull pobiera docelową gałąź, do której chcesz wysłać zmiany, oraz adres URL repozytorium Gita, z którego chcesz pobrać zmiany, a następnie generuje podsumowanie zmian, które będziesz wysyłał. Na przykład, jeżeli Jessica chce wysłać do Johna pull request , a wykonała dwie zmiany na swojej gałęzi tematycznej, którą właśnie wypchnęła, to może wydać poniższe polecenia: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: John Smith (1): added a new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Wynik tej komendy może być wysłany do opiekuna – mówi on z której gałęzi pochodzą zmiany, podsumowuje commity, oraz pokazuje skąd można je pobrać. W projekcie w którym nie jesteś opiekunem, najprostszym sposobem jest utrzymywanie gałęzi master która śledzi origin/master , a wprowadzać zmiany w tematycznych gałęziach, które możesz łatwo usunąć jeżeli zostaną odrzucone. Posiadanie oddzielnych gałęzi dla różnych funkcjonalności, ułatwia również Tobie zmianę bazy ("rebase") jeżeli główna gałąź zostanie zmieniona i przygotowana poprawka nie może się poprawnie nałożyć. Na przykład, jeżeli chcesz wysłać drugi zestaw zmian do projektu, nie kontynuuj pracy na gałęzi którą właśnie wypchnąłeś – rozpocznij nową z gałąź master : $ git checkout -b featureB origin/master # (zmiany) $ git commit $ git push myfork featureB # (e-mail do opiekuna) $ git fetch origin Teraz, każdy z zestawów zmian przechowywany jest w formie silosu – podobnego do kolejki z poprawkami – które możesz nadpisać, zmienić, bez konieczności nachodzenia na siebie, tak jak przedstawiono to poniżej: Figure 70. Początkowa historia zmian z poprawkami z gałęzi featureB . Załóżmy, że opiekun projektu pobrał Twoje zmiany i sprawdził Twoją pierwszą gałąź, ale niestety nie łączy się ona bez przeszkód. W takiej sytuacji, możesz spróbować wykonać rebase na gałęzi origin/master , rozwiązać konflikty i ponownie wysłać zmiany: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA Przepisuje to Twoją historię zmian, która wygląda teraz tak: Figure 71. Historia zmian po pracach na gałęzi featureA . Z powodu zmiany bazy ( rebase ) na gałęzi, musisz użyć przełącznika -f do komendy push , tak abyś na serwerze mógł nadpisać gałąź featureA commitem, który nie jest jej potomkiem. Alternatywą może być wysłanie tych zmian do nowej gałęzi na serwerze (np. nazwanej featureAv2 ). Spójrzmy na jeszcze jeden scenariusz. Opiekun spojrzał na zmiany w Twojej drugiej gałęzi i spodobał mu się pomysł, ale chciałby abyś zmienił sposób w jaki je zaimplementowałeś. Skorzystasz również z okazji, aby przenieść pracę na aktualną gałąź master projektu. Tworzysz więc nową gałąź bazując na origin/master , złączasz tam zmiany z gałęzi featureB , rozwiązujesz ewentualne konflikty, wprowadzasz zmiany w implementacji i następnie wypychasz zmiany do nowej gałęzi: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB # (zmiany w implementacji) $ git commit $ git push myfork featureBv2 Opcja --squash bierze całą pracę wykonaną w połączonej gałęzi i łączy ją w jeden zestaw zmian, tworząc stan repozytorium tak jakby nastąpiło prawdziwe scalenie, bez faktycznego wykonywania commitu scalającego. Oznacza to, że Twój przyszły commit będzie miał tylko jednego rodzica i pozwala na wprowadzenie wszystkich zmian z innej gałęzi, a następnie dokonanie kolejnych zmian przed zarejestrowaniem nowego commitu. Również opcja --no-commit może być przydatna do opóźnienia commitu scalającego w przypadku domyślnego procesu scalania. Teraz możesz wysłać do opiekuna wiadomość, że wprowadziłeś wszystkie wymagane zmiany, które może znaleźć w gałęzi featureBv2 . Figure 72. Historia zmian po zmianach w gałęzi featureBv2 . Publiczne projekty poprzez e-mail Duża ilość większych projektów ma ustalone reguły dotyczące akceptowania poprawek – będziesz musiał sprawdzić konkretne zasady dla każdego z projektów, ponieważ będą się różniły. Jednak sporo większych projektów akceptuje poprawki poprzez listy mailingowe przeznaczone dla programistów, dlatego też teraz opiszemy ten przykład. Przepływ pracy jest podobny do poprzedniego – tworzysz tematyczne gałęzie dla każdej grupy zmian, nad którymi pracujesz. Różnica polega na tym, w jaki sposób wysyłasz je do projektu. Zamiast tworzyć rozwidlenie ( fork ) i wypychać do niego zmiany, tworzysz wiadomość e-mail dla każdego zestawu zmian i wysyłasz je na listę mailingową: $ git checkout -b topicA # (zmiany) $ git commit # (zmiany) $ git commit Teraz masz dwa commity, które chcesz wysłać na listę dyskusyjną. Użyj git format-patch do wygenerowania plików w formacie mbox , które możesz wysłać na listę – zamieni to każdy commit w osobną wiadomość, z pierwszą linią komentarza ("commit message") jako tematem, jego pozostałą częścią w treści, dołączając jednocześnie zawartość wprowadzanej zmiany. Miłą rzeczą jest to, że aplikowanie poprawki przesłanej przez e-mail i wygenerowanej za pomocą format-patch zachowuje wszystkie informacje o commicie. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Komenda format-patch wypisuje nazwy plików, które stworzyła. Opcja -M mówi Git, aby brał pod uwagę również zmiany nazw plików. Zawartość plików w efekcie końcowym wygląda tak: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 Możesz oczywiście zmienić te pliki i dodać większą ilość informacji w mailu, których nie chciałeś pokazywać w komentarzu do zmiany. Jeżeli dodasz tekst miedzy linię --- a początkiem poprawki (linia diff --git ), programiści będą mogli to przeczytać, ale wdrażanie poprawki pominie te fragmenty. Aby wysłać to na listę mailingową, możesz albo wkleić zawartość plików w programie e-mail lub użyć programu uruchamianego z linii komend. Wklejanie tekstu często wprowadza problemy z zachowaniem formatowania, szczególnie przy użyciu tych "mądrzejszych" programów pocztowych, które nie zachowują poprawnie znaków nowej linii i spacji. Na szczęście Git udostępnia narzędzie, które pomoże Ci wysłać poprawnie sformatowane poprawki poprzez protokół IMAP, może to być łatwiejsze dla Ciebie. Pokażemy w jaki sposób wysyłać poprawki przy pomocy Gmaila, który tak się składa, że jest agentem poczty elektronicznej, którego znamy najlepiej. Możesz znaleźć bardziej szczegółowe instrukcje dla różnych programów pocztowych na końcu wcześniej wymienionego pliku Documentation/SubmittingPatches , który znajduje się w kodzie źródłowym Gita. Najpierw musisz ustawić sekcję imap` w swoim pliku ~/.gitconfig . Możesz ustawić każdą wartość oddzielnie przy pomocy kilku komend git config lub możesz je dodać ręcznie, jednak w efekcie Twój plik konfiguracyjny powinien wyglądać podobnie do poniższego: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = p4ssw0rd port = 993 sslverify = false Jeżeli Twój serwer IMAP nie używa SSL, to dwie ostatnie linie prawdopodobnie nie są potrzebne, a w polu host będzie imap:// zamiast imaps:// . Po takiej konfiguracji możesz używać komendy git imap-send aby umieścić poprawki w folderze "Wersje robocze" ("Draft") na podanym serwerze IMAP: $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done W tym momencie powinieneś być w stanie przejść do swojego folderu "Wersje robocze", zmienić pole "Do" ("To") na listę mailingową, na którą wysyłasz poprawkę, ewentualnie dodać w "DW" ("Do wiadomości", ang. "CC" czyli "Carbon Copy") adres e-mail opiekuna lub osoby odpowiedzialnej za daną sekcję, i ostatecznie wysłać e-maila. Możesz także wysyłać poprawki przez serwer SMTP. Tak jak poprzednio, możesz ustawić każdą wartość osobno za pomocą serii komend git config lub możesz dodać je ręcznie w sekcji sendemail w swoim pliku ~/.gitconfig : [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 Po wykonaniu tych czynności, możesz użyć komendy git send-email do wysłania swoich poprawek: $ git send-email *.patch 0001-added-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Następnie Git wyświetla dla każdej wysyłanej poprawki kilka informacji, które wyglądają mniej więcej tak: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] added limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Podsumowanie Powyższa sekcja opisywała kilka z najczęściej używanych sposobów przepływu pracy z różnymi projektami Git, które możesz spotkać, oraz wprowadziła kilka nowych narzędzi ułatwiajacych ten proces. W następnych sekcjach zobaczysz jak wygląda praca nad projektem, ale z drugiej strony: będzie to utrzymywanie projektu Git. Nauczysz się jak być miłosiernym dyktatorem oraz osobą integrującą zmiany innych osób. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/GitHub-%d0%a3%d0%bf%d1%80%d0%b0%d0%b2%d0%bb%d0%b5%d0%bd%d0%b8%d0%b5-%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%b5%d0%ba%d1%82 | Git - Управление на проект About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 4.3 GitHub - Управление на проект Управление на проект След като вече сме готови да сътрудничим в проекти на други хора, ще погледнем и обратната страна: създаване, поддържане и администриране на собствен проект. Създаване на хранилище Нека създадем ново хранилище, чийто код да споделим с другите. Започваме натискайки бутона “New repository” в дясната част на екрана или натискайки бутона + в горния тулбар до потребителското ни име както можем да видим в Падащият списък “New repository” . Фигура 109. Частта “Your repositories” Фигура 110. Падащият списък “New repository” Това ни прехвърля към формата “new repository”: Фигура 111. Формата “new repository” На практика, единственото задължително поле е това с името на проекта, всички останали са незадължителни. Засега просто натиснете бутона “Create Repository” и вече разполагате с ново хранилище в GitHub, с име <user>/<project_name> . Понеже все още нямате качен никакъв код, GitHub ще ви предложи инструкции как да създадете ново Git хранилище или да се свържете със съществуващ Git проект. Няма да навлизаме в детайли за това, ако имате нужда от припомняне, погледнете Основи на Git . Сега проектът ви се хоства в GitHub и можете да изпратите URL-а на всеки, с който желаете да го споделите. Всеки GitHub проект е достъпен през HTTPS като https://github.com/<user>/<project_name> , а също и през SSH като git@github.com:<user>/<project_name> . Git може да тегли и да изпраща и по двата начина, а достъпът се контролира с правата на името и паролата на свързващия се потребител. Забележка Често се предпочита HTTPS-базиран достъп, понеже по този начин външният потребител може да клонира проект и без да има GitHub акаунт. Ако някой потребител предпочита SSH достъп, то той трябва да има акаунт и качен SSH ключ. HTTPS адресът е същият, който потребителят би написал в браузъра си за уеб базиран достъп до проекта. Добавяне на сътрудници Ако работите с други хора по проекта си и желаете да им дадете възможност да правят къмити, трябва да ги добавите към проекта като “collaborators”. Ако Ben, Jeff, и Louise имат GitHub акаунти и искате да има дадете Push достъп до вашето хранилище, можете да ги добавите към проекта, така че да могат както да четат, така и да пишат в кода. Натиснете линка “Settings” в дъното на дясната част. Фигура 112. Препратката settings за хранилището След това, изберете “Collaborators” от менюто вляво. Въведете потребителското име, което желаете и щракнете"`Add collaborator.`" Можете да повторите това за колкото други потребителя желаете. Ако искате пък да отнемете достъпа, просто щракнете “X” иконата в дясната част на съответния ред. Фигура 113. Сътрудници в хранилище Управление на Pull Requests Сега вече имате проект с код в него и може би няколко сътрудника с push достъп до хранилището - нека да видим какво да направите, когато получите Pull Request. Pull Request-ите могат да дойдат от клон, който се намира във fork на проекта ви или пък от друг клон в същото хранилище. Единствената разлика е, че в клоновете на fork-натите хранилища нормално нямате достъп за писане (а и собствениците им нямат към вашите клонове), докато при вътрешните Pull Request-и обикновено и двете страни могат да пишат в клона. За тези примери, нека приемем, че вие сте потребител “tonychacon” и сте създали нов Arduino проект наречен “fade”. Email известяване Някой се появява, променя част от кода ви и ви изпраща Pull Request. Ще получите електронна поща за новия Pull Request изглеждащ подобно на Email известяване за нов Pull Request . Фигура 114. Email известяване за нов Pull Request Няколко неща са за отбелязване в този имейл. Първо, той съдържа малък diffstat — списък на файловете, в които има промени от Pull Request-а и в какво количество са те. След това, имате линк към Pull Request-а в GitHub. Предоставят ви се и няколко URL-а, които можете да ползвате от командния ред. Ако виждате ред git pull <url> patch-1 , това е прост начин да слеете отдалечен клон без да трябва да добавяте remote. Видяхме това в Извличане от отделечени клонове . Ако искате, можете да създадете и да превключите в topic клон и след това да изпълните тази команда за да слеете Pull Request-а. Другите интересни URL-и са .diff и .patch URL-ите, които както можете да предположите, осигуряват unified diff и patch версии на Pull Request-а. Технически, можете да слеете работата в Pull Request-а примерно така: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Съвместна работа по Pull Request Както видяхме в Работния процес в GitHub , сега можете да проведете дискусия с човека, който е пуснал Pull Request-а. Можете да коментирате специфични редове код, да коментирате цели къмити или целия Pull Request, използвайки GitHub Flavored Markdown където искате. Всеки път, когато някой друг коментира Pull Request-а, ще продължавате да получавате имейл нотификации, така че да сте наясно какво се случва. Всеки от дискутиращите ще има линк към Pull Request-а и също така можете директно да отговорите на имейла пускайки автоматично коментар в Pull Request нишката в GitHub. Фигура 115. Отговорите на имейлите се показват в нишката Веднъж след като кодът е одобрен и искате да го слеете, можете или да го издърпате и слеете локално с помощта на git pull <url> <branch> синтаксиса, който видяхме по-рано, или да добавите fork-хранилището като remote, да го изтеглите и слеете. Ако сливането е просто, можете направо да натиснете бутона “Merge” в GitHub. Това ще направи “non-fast-forward” сливане с merge commit, дори и ако е възможно fast-forward сливане. Всеки път когато използвате бутона, винаги се създава merge commit независимо от обстоятелствата. Както можете да видите в Merge бутон и инструкции за сливането на Pull Request-а ръчно , GitHub ви дава цялата тази информация ако натиснете помощната препратка. Фигура 116. Merge бутон и инструкции за сливането на Pull Request-а ръчно Ако решите, че не искате да слеете, можете просто да затворите Pull Request-а и човекът, който го е стартирал ще бъде уведомен. Pull Request референции Ако си имате работа с много Pull Request-и и не искате да добавяте цял куп remotes или да правите еднократни изтегляния всеки път, GitHub ви предоставя един хитър трик за улеснение в работата. Това е материал за напреднали и ще видим детайлите за него в Refspec спецификации , но може да е много полезен. GitHub в действителност представя Pull Request клоновете за дадено хранилище като вид псевдо-клонове на сървъра. По подразбиране, вие не ги получавате при клониране, но те са там по един маскиран начин и можете да получите достъп до тях лесно. За да демонстрираме това, ще използваме low-level команда (често наричана “plumbing” команда, за която ще научим повече в Plumbing и Porcelain команди ) наречена ls-remote . Обикновено тази команда не се използва ежедневно в Git операциите, но е полезна защото ни показва какви референции съществуват на сървъра. Ако стартираме тази команда за “blink” хранилището, което ползвахме по-рано, ще видим списък от всички клонове, тагове и други референции в него. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Разбира се, ако сте във вашето хранилище и изпълните git ls-remote origin или кой да е друг remote, ще видите отпечатан изход подобен на този. Ако хранилището е в GitHub и имате отворени Pull Request-и, ще получите тези референции с префикс refs/pull/ . Това по същество са клонове, но понеже не са под refs/heads/ , нормално не ги получавате когато клонирате или изтегляте от сървъра — fetching процесът по подразбиране ги игнорира. Има по две референции на Pull Request - едната която завършва на /head сочи към точно същия къмит както и последния къмит в Pull Request клона. По този начин, ако някой отвори Pull Request в наше хранилище и клонът му се казва bug-fix , сочещ към къмит a5a775 , тогава в нашето хранилище ние няма да имаме bug-fix клон (той е във fork-а), но ще имаме pull/<pr#>/head референция сочеща към a5a775 . Това означава, че можем лесно да изтеглим всеки Pull Request клон в една стъпка без да трябва да добавяме множество remotes. Сега можем да изтеглим референцията директно. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Това инструктира Git да се свърже с origin адреса и да изтегли референцията наречена refs/pull/958/head . Git за щастие следва инструкцията и сваля всичко необходимо за конструирането на тази референция, след което поставя указател към къмита, който искате в .git/FETCH_HEAD . Можете да продължите с git merge FETCH_HEAD в клон, в който да тествате, но merge commit съобщението изглежда леко странно. Също така, ако разглеждате много Pull Request-и, това става досадно Съществува също начин да изтеглите всички Pull Request-и и да ги актуализирате всеки път, когато се свързвате с отдалечения сървър. Отворете файла .git/config и потърсете origin секцията. Ще изглежда по подобен начин: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Редът , който започва с fetch = се нарича “refspec.” Това е начин за съотнасяне на имена в сървъра с имена в локалната ви .git директория. В примера тук, това казва на Git, "нещата на сървъра, които се намират в refs/heads трябва да се съхраняват в локалното ми хранилище в refs/remotes/origin ." Можете да промените тази секция за да добавите друг refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Това инструктира Git че, “всички refs изглеждащи като refs/pull/123/head трябва да се съхраняват локално като refs/remotes/origin/pr/123 .” Сега, ако запишете файла и изпълните git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Сега всички отдалечени Pull Request-и се представят локално като refs, които работят като tracking клонове - те са само за четене и се обновяват когато теглите. Това прави много лесно изпробването на код от Pull Request локално: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' Наблюдателните читатели ще забележат надписа head в края на remote частта на refspec. Съществува също и refs/pull/#/merge референция от страна на GitHub, която представлява къмита, който ще се създаде ако натиснете бутона “merge” в сайта. Това може да ви позволи да тествате сливането преди още да сте натиснали бутона. Pull Requests на Pull Requests Можете да създавате Pull Request-и насочени не само към главния ( master ) клон, а към всеки един клон в мрежата. В действителност, можете да ги насочите и към друг Pull Request. Ако забележите Pull Request, който се развива в добра посока и имате идея за подобряване на кода в него, или пък просто нямате push достъп до желания клон, можете да отворите отделен Pull Request директно към него. Когато започвате да правите Pull Request, в горната част на екрана има кутия, указваща от и към кой клон опитвате да го насочите. Ако натиснете бутона “Edit” вдясно от кутията, можете да смените не само клоновете, но и fork-а. Фигура 117. Ръчна смяна на целевия клон и fork на Pull Request Тук можете сравнително лесно да слеете вашия нов клон в друг Pull Request или друг fork на проекта. Бележки и уведомления GitHub също така има удобна система за нотификации, която е полезна, когато имате въпроси или ви трябва мнение от специфични разработчици или екипи. Във всеки коментар, можете да въведете символа @ и ще получите autocomplete списък с имената и потребителските имена на сътрудниците в проекта. Фигура 118. Въведете @ за да упоменете някого Можете да упоменете и потребител, който не се показва в списъка, но често списъкът ускорява нещата. След като веднъж публикувате коментар с упоменат по горния начин потребител, той ще бъде уведомен за това. Това е доста ефективен начин да въведете хора в дискусия, вместо да разчитате те да я наблюдават. Много често в Pull Request-ите в GitHub разработчиците използват този похват, за да привлекат вниманието на колегите си към даден Issue или Pull Request. Ако някой е бил упоменат в Pull Request или Issue, той ще бъде “абониран” към тях и ще бъде осведомяван своевременно за възникнала активност. Ще бъдете абонирани също така за всичко, което сте стартирали, за събития в наблюдавани хранилища или когато коментирате нещо. Ако не желаете да получавате нотификации, в съответната страница има бутон “Unsubscribe”, с който да се отпишете от уведомяванията свързани с нея. Фигура 119. Отписване от нотификации за Issue или Pull Request Страницата за уведомления Под “нотификации” в смисъла на GitHub имаме предвид специфичния подход, който сайтът използва за да поддържа връзка с вас при възникнали събития. Съществуват няколко различни начина за тяхната настройка. Ако отворите секцията “Notification center” от страницата с настройки можете да видите част от наличните опции. Фигура 120. Опции за известяване Двата избора за получаване на известия са през “Email” и “Web” и може да изберете кой да е от двата, двата едновременно или пък нито един Web известяване Web известяванията се отнасят само до сайта GitHub и можете да ги виждате само там. Ако в предпочитанията си сте избрали тази опция и възникне касаещо ви събитие, ще видите малка синя точка над иконата за нотификации в горната част на екрана както е показано в Център за известия . Фигура 121. Център за известия Ако щракнете върху нея, ще се покаже списък с всички уведомления за вас, групирани по проект. Можете да филтрирате по конкретен проект щракайки върху името му в лявата лента. Можете да маркирате уведомлението като прието с чекбокс иконата до него или да маркирате всички като приети с чекбокса в горната част на групата. Съществува и бутон mute до всеки чекбокс, чрез който да укажете, че не желаете повече уведомления по съответната нотификация. Всички тези инструменти са полезни при работа с голям брой известия. Много от опитните GitHub потребители изключват изцяло имейл уведомленията и управляват известията си през този екран. Email известяване Email опцията е алтернативен начин за управление на известяванията през GitHub. Ако я използвате, ще получавате поща за всяко известяване. Видяхме примери за това в Коментарите изпратени като имейл уведомление и Email известяване за нов Pull Request . Пощите също така ще бъдат правилно подредени в нишки, което е чудесно ако използвате threading съвместим пощенски клиент. Хедърите на имейл съобщенията съдържат съответните метаданни, което е полезно за създаването на специфични правила и филтри за обслужването им от клиента. Например, ако разгледаме хедърите на писмото до Tony показано в Email известяване за нов Pull Request , ще забележим следното: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Тук има няколко интересни неща. Ако искате да осветите или препратите имейлите от този конкретен проект или дори Pull Request, информацията в хедъра Message-ID ви дава всички данни във формата <user>/<project>/<type>/<id> . Ако например пощата се отнася до даден Issue, тогава <type> полето ще е “issues” вместо “pull”. List-Post и List-Unsubscribe хедърите помагат на съвместимите имейл клиенти бързо да изпратят отговор или да се отпишат от дискусията. По същество ефектът е същия както ако натиснете “mute” бутона в сайта или “Unsubscribe” в Issue или Pull Request страница. Ако сте активирали и двата вида уведомявания и прочетете имейл версията за дадено събитие, то уеб версията му също ще бъде маркирана като прочетена (ако имейл клиентът ви разрешава картинки). Специални файлове Съществуват няколко специални файла, които GitHub ще забележи, ако присъстват в хранилището ви. README Първият е README файла, който може да се форматира във всеки формат, който GitHub би разпознал. Например, може да е README , README.md , README.asciidoc , и т.н. Ако GitHub види README файл, ще го рендерира на началната страница на проекта. Много екипи ползват това за представяне на най-важните аспекти от проекта пред незапознатите с него потребители. Това би могло да включва: Каква е целта на проекта Как се конфигурира и инсталира Пример за това как се ползва и пуска Лицензът, под който се публикува Указания за сътрудничество в него Понеже GitHub рендерира този файл, можете да вмъквате линкове (вкл. и към изображения) за допълнително улеснение на разглеждащия. CONTRIBUTING Друг специален файл, който GitHub разпознава е CONTRIBUTING файла. Ако имате файл с това име и произволно разширение, то GitHub ще покаже Създаване на Pull Request при наличен CONTRIBUTING файл , когато някой започне да създава Pull Request. Фигура 122. Създаване на Pull Request при наличен CONTRIBUTING файл Идеята тук е да покажете специфичните неща, които искате или не желаете да присъстват в Pull Request-ите към проекта ви. Така потребителите могат да прочетат изискванията ви преди да създадат Pull Request. Администриране на проект В общи линии броят на административните действия за единичен проект не е голям, но има няколко интересни опции. Смяна на клона по подразбиране Ако ползвате име на клон по подразбиране различно от “master” за основния клон, можете да укажете това в секцията “Options” в страницата с настройки за хранилището. Фигура 123. Смяна на клона по подразбиране за проект Просто сменете клона по подразбиране от падащия списък и той ще стане такъв за всички главни действия занапред, включително за това от кой клон ще се извлекат файловете на проекта когато някой клонира хранилището. Трансфер на проект Ако искате да прехвърлите проекта си към друг потребител или организация в GitHub, разполагате с опция “Transfer ownership” в долната част на същата “Options” секция от настройките на проекта. Фигура 124. Трансфер на проект към друг GitHub потребител или организация Това е полезно, ако прекратявате участието си в проект и някой друг иска да продължи поддръжката му или пък ако даден проект стане твърде мащабен и бихте желали да го преместите в организация. Това не само ще премести хранилището заедно с всичката информация за него към друго място, но също така и ще бъде създаден redirect URL към новото място. Клониранията и изтеглянията от Git също ще бъдат пренасочени, а не само за уеб заявките. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/uk/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-Git-%d0%9f%d1%96%d0%b4%d1%81%d1%83%d0%bc%d0%be%d0%ba | Git - Підсумок About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 2.8 Основи Git - Підсумок Підсумок На цей час, ви можете робити всі основні операції Git - створювати або клонувати репозиторій, вносити зміни, індексувати зміни та створювати коміти, переглядати історію всіх змін у репозиторії. Далі, ми розглянемо вбивчу особливість Git: його моделі галуження. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.notion.com/es/product/calendar/download | Notion Calendar para Mac Notion Funciones IA de Notion Crea, escribe, automatiza Agentes Gestiona las tareas manuales Búsqueda Enterprise Encuentra respuestas al instante Anotador con IA Escritas a la perfección por la IA Documentos Sencillos y potentes Base de conocimiento Centraliza tus conocimientos Proyectos Gestiona cualquier proyecto Sites Publica lo que quieras sin demoras Primeros pasos Explora casos de uso de la IA Descubre todo lo que la IA de Notion puede hacer Explora Marketplace Plantillas para cada necesidad Conoce las integraciones Conecta tus apps con Notion Descarga Web Clipper Guarda páginas de la web en Notion Prueba la app de escritorio de Notion para disfrutar de una experiencia más rápida Descarga la app Mail Calendar IA Enterprise Precios Explora Equipos Desarrollo y Producto Diseño Marketing TI Tamaño del equipo Start-ups Pymes Enterprise Educación Aprende Centro de ayuda Notion Academy Historias de clientes Blog Comunidad Programas para socios Crea API Plantillas Seguridad Consultores Solicita una demo Inicia sesión Obtén Notion gratis Notion Calendar es más potente en la versión de escritorio Mayor velocidad y distracciones mínimas. Descargar para Mac → Notion Calendar está disponible en navegadores de escritorio, macOS, Windows, iOS y Android. Español (Latinoamérica) Configuración de cookies © 2026 Notion Labs, Inc. Empresa Conócenos Oportunidades laborales Seguridad Estado Términos de uso y privacidad Tus derechos de privacidad Descargar iOS y Android Mac y Windows Calendario Web Clipper Recursos Centro de ayuda Precios Blog Comunidad Integraciones Plantillas Programas para socios Notion para Enterprise Pequeña empresa Personal Descubre más → | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%9e%d0%b1%d0%be%d0%b1%d1%89%d0%b5%d0%bd%d0%b8%d0%b5 | Git - Обобщение About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.15 Git инструменти - Обобщение Обобщение Разгледахме множество разширени инструменти, позволяващи ви да манипулирате вашите къмити и индексната област по прецизен начин. Когато срещнете проблем, би следвало да можете лесно да откриете кой къмит го е причинил, кога и от кого идва. Ако искате да ползвате вложени проекти (подмодули) в основния такъв, научихте как да го направите. На този етап, вече би следвало комфортно да можете да правите повечето неща в Git, от които ще имате нужда в ежедневната си работа. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/be/v2/Distributed-Git-Contributing-to-a-Project | Git - Contributing to a Project About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Distributed Git - Contributing to a Project Contributing to a Project The main difficulty with describing how to contribute to a project are the numerous variations on how to do that. Because Git is very flexible, people can and do work together in many ways, and it’s problematic to describe how you should contribute — every project is a bit different. Some of the variables involved are active contributor count, chosen workflow, your commit access, and possibly the external contribution method. The first variable is active contributor count — how many users are actively contributing code to this project, and how often? In many instances, you’ll have two or three developers with a few commits a day, or possibly less for somewhat dormant projects. For larger companies or projects, the number of developers could be in the thousands, with hundreds or thousands of commits coming in each day. This is important because with more and more developers, you run into more issues with making sure your code applies cleanly or can be easily merged. Changes you submit may be rendered obsolete or severely broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next variable is the workflow in use for the project. Is it centralized, with each developer having equal write access to the main codeline? Does the project have a maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your work to them first? The next variable is your commit access. The workflow required in order to contribute to a project is much different if you have write access to the project than if you don’t. If you don’t have write access, how does the project prefer to accept contributed work? Does it even have a policy? How much work are you contributing at a time? How often do you contribute? All these questions can affect how you contribute effectively to a project and what workflows are preferred or available to you. We’ll cover aspects of each of these in a series of use cases, moving from simple to more complex; you should be able to construct the specific workflows you need in practice from these examples. Commit Guidelines Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file. First, your submissions should not contain any whitespace errors. Git provides an easy way to check for this — before you commit, run git diff --check , which identifies possible whitespace errors and lists them for you. Малюнак 56. Output of git diff --check If you run that command before committing, you can tell if you’re about to commit whitespace issues that may annoy other developers. Next, try to make each commit a logically separate changeset. If you can, try to make your changes digestible — don’t code for a whole weekend on five different issues and then submit them all as one massive commit on Monday. Even if you don’t commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit. If some of the changes modify the same file, try to use git add --patch to partially stage files (covered in detail in Interactive Staging ). The project snapshot at the tip of the branch is identical whether you do one commit or five, as long as all the changes are added at some point, so try to make things easier on your fellow developers when they have to review your changes. This approach also makes it easier to pull out or revert one of the changesets if you need to later. Rewriting History describes a number of useful Git tricks for rewriting history and interactively staging files — use these tools to help craft a clean and understandable history before sending the work to someone else. The last thing to keep in mind is the commit message. Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior — this is a good guideline to follow. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." Here is a template you can follow, which we’ve lightly adapted from one originally written by Tim Pope : Capitalized, short (50 chars or less) summary More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase will confuse you if you run the two together. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like git merge and git revert. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, followed by a single space, with blank lines in between, but conventions vary here - Use a hanging indent If all your commit messages follow this model, things will be much easier for you and the developers with whom you collaborate. The Git project has well-formatted commit messages — try running git log --no-merges there to see what a nicely-formatted project-commit history looks like. Заўвага Do as we say, not as we do. For the sake of brevity, many of the examples in this book don’t have nicely-formatted commit messages like this; instead, we simply use the -m option to git commit . In short, do as we say, not as we do. Private Small Team The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository. In this environment, you can follow a workflow similar to what you might do when using Subversion or another centralized system. You still get the advantages of things like offline committing and vastly simpler branching and merging, but the workflow can be very similar; the main difference is that merges happen client-side rather than on the server at commit time. Let’s see what it might look like when two developers start to work together with a shared repository. The first developer, John, clones the repository, makes a change, and commits locally. The protocol messages have been replaced with … in these examples to shorten them somewhat. # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'Remove invalid default value' [master 738ee87] Remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) The second developer, Jessica, does the same thing — clones the repository and commits a change: # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'Add reset task' [master fbff5bc] Add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Now, Jessica pushes her work to the server, which works just fine: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master The last line of the output above shows a useful return message from the push operation. The basic format is <oldref>..<newref> fromref → toref , where oldref means the old reference, newref means the new reference, fromref is the name of the local reference being pushed, and toref is the name of the remote reference being updated. You’ll see similar output like this below in the discussions, so having a basic idea of the meaning will help in understanding the various states of the repositories. More details are available in the documentation for git-push . Continuing with this example, shortly afterwards, John makes some changes, commits them to his local repository, and tries to push them to the same server: # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' In this case, John’s push fails because of Jessica’s earlier push of her changes. This is especially important to understand if you’re used to Subversion, because you’ll notice that the two developers didn’t edit the same file. Although Subversion automatically does such a merge on the server if different files are edited, with Git, you must first merge the commits locally. In other words, John must first fetch Jessica’s upstream changes and merge them into his local repository before he will be allowed to push. As a first step, John fetches Jessica’s work (this only fetches Jessica’s upstream work, it does not yet merge it into John’s work): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master At this point, John’s local repository looks something like this: Малюнак 57. John’s divergent history Now John can merge Jessica’s work that he fetched into his own local work: $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) As long as that local merge goes smoothly, John’s updated history will now look like this: Малюнак 58. John’s repository after merging origin/master At this point, John might want to test this new code to make sure none of Jessica’s work affects any of his and, as long as everything seems fine, he can finally push the new merged work up to the server: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master In the end, John’s commit history will look like this: Малюнак 59. John’s history after pushing to the origin server In the meantime, Jessica has created a new topic branch called issue54 , and made three commits to that branch. She hasn’t fetched John’s changes yet, so her commit history looks like this: Малюнак 60. Jessica’s topic branch Suddenly, Jessica learns that John has pushed some new work to the server and she wants to take a look at it, so she can fetch all new content from the server that she does not yet have with: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master That pulls down the work John has pushed up in the meantime. Jessica’s history now looks like this: Малюнак 61. Jessica’s history after fetching John’s changes Jessica thinks her topic branch is ready, but she wants to know what part of John’s fetched work she has to merge into her work so that she can push. She runs git log to find out: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 Remove invalid default value The issue54..origin/master syntax is a log filter that asks Git to display only those commits that are on the latter branch (in this case origin/master ) that are not on the first branch (in this case issue54 ). We’ll go over this syntax in detail in Commit Ranges . From the above output, we can see that there is a single commit that John has made that Jessica has not merged into her local work. If she merges origin/master , that is the single commit that will modify her local work. Now, Jessica can merge her topic work into her master branch, merge John’s work ( origin/master ) into her master branch, and then push back to the server again. First (having committed all of the work on her issue54 topic branch), Jessica switches back to her master branch in preparation for integrating all this work: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jessica can merge either origin/master or issue54 first — they’re both upstream, so the order doesn’t matter. The end snapshot should be identical no matter which order she chooses; only the history will be different. She chooses to merge the issue54 branch first: $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) No problems occur; as you can see it was a simple fast-forward merge. Jessica now completes the local merging process by merging John’s earlier fetched work that is sitting in the origin/master branch: $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Everything merges cleanly, and Jessica’s history now looks like this: Малюнак 62. Jessica’s history after merging John’s changes Now origin/master is reachable from Jessica’s master branch, so she should be able to successfully push (assuming John hasn’t pushed even more changes in the meantime): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Each developer has committed a few times and merged each other’s work successfully. Малюнак 63. Jessica’s history after pushing all changes back to the server That is one of the simplest workflows. You work for a while (generally in a topic branch), and merge that work into your master branch when it’s ready to be integrated. When you want to share that work, you fetch and merge your master from origin/master if it has changed, and finally push to the master branch on the server. The general sequence is something like this: Малюнак 64. General sequence of events for a simple multiple-developer Git workflow Private Managed Team In this next scenario, you’ll look at contributor roles in a larger private group. You’ll learn how to work in an environment where small groups collaborate on features, after which those team-based contributions are integrated by another party. Let’s say that John and Jessica are working together on one feature (call this “featureA”), while Jessica and a third developer, Josie, are working on a second (say, “featureB”). In this case, the company is using a type of integration-manager workflow where the work of the individual groups is integrated only by certain engineers, and the master branch of the main repo can be updated only by those engineers. In this scenario, all work is done in team-based branches and pulled together by the integrators later. Let’s follow Jessica’s workflow as she works on her two features, collaborating in parallel with two different developers in this environment. Assuming she already has her repository cloned, she decides to work on featureA first. She creates a new branch for the feature and does some work on it there: # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'Add limit to log function' [featureA 3300904] Add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) At this point, she needs to share her work with John, so she pushes her featureA branch commits up to the server. Jessica doesn’t have push access to the master branch — only the integrators do — so she has to push to another branch in order to collaborate with John: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica emails John to tell him that she’s pushed some work into a branch named featureA and he can look at it now. While she waits for feedback from John, Jessica decides to start working on featureB with Josie. To begin, she starts a new feature branch, basing it off the server’s master branch: # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Now, Jessica makes a couple of commits on the featureB branch: $ vim lib/simplegit.rb $ git commit -am 'Make ls-tree function recursive' [featureB e5b0fdc] Make ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'Add ls-files' [featureB 8512791] Add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Jessica’s repository now looks like this: Малюнак 65. Jessica’s initial commit history She’s ready to push her work, but gets an email from Josie that a branch with some initial “featureB” work on it was already pushed to the server as the featureBee branch. Jessica needs to merge those changes with her own before she can push her work to the server. Jessica first fetches Josie’s changes with git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Assuming Jessica is still on her checked-out featureB branch, she can now merge Josie’s work into that branch with git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) At this point, Jessica wants to push all of this merged “featureB” work back to the server, but she doesn’t want to simply push her own featureB branch. Rather, since Josie has already started an upstream featureBee branch, Jessica wants to push to that branch, which she does with: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee This is called a refspec . See The Refspec for a more detailed discussion of Git refspecs and different things you can do with them. Also notice the -u flag; this is short for --set-upstream , which configures the branches for easier pushing and pulling later. Suddenly, Jessica gets email from John, who tells her he’s pushed some changes to the featureA branch on which they are collaborating, and he asks Jessica to take a look at them. Again, Jessica runs a simple git fetch to fetch all new content from the server, including (of course) John’s latest work: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessica can display the log of John’s new work by comparing the content of the newly-fetched featureA branch with her local copy of the same branch: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 Increase log output to 30 from 25 If Jessica likes what she sees, she can merge John’s new work into her local featureA branch with: $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Finally, Jessica might want to make a couple minor changes to all that merged content, so she is free to make those changes, commit them to her local featureA branch, and push the end result back to the server: $ git commit -am 'Add small tweak to merged content' [featureA 774b3ed] Add small tweak to merged content 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Jessica’s commit history now looks something like this: Малюнак 66. Jessica’s history after committing on a feature branch At some point, Jessica, Josie, and John inform the integrators that the featureA and featureBee branches on the server are ready for integration into the mainline. After the integrators merge these branches into the mainline, a fetch will bring down the new merge commit, making the history look like this: Малюнак 67. Jessica’s history after merging both her topic branches Many groups switch to Git because of this ability to have multiple teams working in parallel, merging the different lines of work late in the process. The ability of smaller subgroups of a team to collaborate via remote branches without necessarily having to involve or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Малюнак 68. Basic sequence of this managed-team workflow Forked Public Project Contributing to public projects is a bit different. Because you don’t have the permissions to directly update branches on the project, you have to get the work to the maintainers some other way. This first example describes contributing via forking on Git hosts that support easy forking. Many hosting sites support this (including GitHub, BitBucket, repo.or.cz, and others), and many project maintainers expect this style of contribution. The next section deals with projects that prefer to accept contributed patches via email. First, you’ll probably want to clone the main repository, create a topic branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Заўвага You may want to use rebase -i to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review — see Rewriting History for more information about interactive rebasing. When your branch work is finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository URL as a new remote of your local repository; in this example, let’s call it myfork : $ git remote add myfork <url> You then need to push your new work to this repository. It’s easiest to push the topic branch you’re working on to your forked repository, rather than merging that work into your master branch and pushing that. The reason is that if your work isn’t accepted or is cherry-picked, you don’t have to rewind your master branch (the Git cherry-pick operation is covered in more detail in Rebasing and Cherry-Picking Workflows ). If the maintainers merge , rebase , or cherry-pick your work, you’ll eventually get it back via pulling from their repository anyhow. In any event, you can push your work with: $ git push -u myfork featureA Once your work has been pushed to your fork of the repository, you need to notify the maintainers of the original project that you have work you’d like them to merge. This is often called a pull request , and you typically generate such a request either via the website — GitHub has its own “Pull Request” mechanism that we’ll go over in GitHub — or you can run the git request-pull command and email the subsequent output to the project maintainer manually. The git request-pull command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and produces a summary of all the changes you’re asking to be pulled. For instance, if Jessica wants to send John a pull request, and she’s done two commits on the topic branch she just pushed, she can run this: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): Create new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): Add limit to log function Increase log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) This output can be sent to the maintainer — it tells them where the work was branched from, summarizes the commits, and identifies from where the new work is to be pulled. On a project for which you’re not the maintainer, it’s generally easier to have a branch like master always track origin/master and to do your work in topic branches that you can easily discard if they’re rejected. Having work themes isolated into topic branches also makes it easier for you to rebase your work if the tip of the main repository has moved in the meantime and your commits no longer apply cleanly. For example, if you want to submit a second topic of work to the project, don’t continue working on the topic branch you just pushed up — start over from the main repository’s master branch: $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Now, each of your topics is contained within a silo — similar to a patch queue — that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so: Малюнак 69. Initial commit history with featureB work Let’s say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges. In this case, you can try to rebase that branch on top of origin/master , resolve the conflicts for the maintainer, and then resubmit your changes: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA This rewrites your history to now look like Commit history after featureA work . Малюнак 70. Commit history after featureA work Because you rebased the branch, you have to specify the -f to your push command in order to be able to replace the featureA branch on the server with a commit that isn’t a descendant of it. An alternative would be to push this new work to a different branch on the server (perhaps called featureAv2 ). Let’s look at one more possible scenario: the maintainer has looked at work in your second branch and likes the concept but would like you to change an implementation detail. You’ll also take this opportunity to move the work to be based off the project’s current master branch. You start a new branch based off the current origin/master branch, squash the featureB changes there, resolve any conflicts, make the implementation change, and then push that as a new branch: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 The --squash option takes all the work on the merged branch and squashes it into one changeset producing the repository state as if a real merge happened, without actually making a merge commit. This means your future commit will have one parent only and allows you to introduce all the changes from another branch and then make more changes before recording the new commit. Also the --no-commit option can be useful to delay the merge commit in case of the default merge process. At this point, you can notify the maintainer that you’ve made the requested changes, and that they can find those changes in your featureBv2 branch. Малюнак 71. Commit history after featureBv2 work Public Project over Email Many projects have established procedures for accepting patches — you’ll need to check the specific rules for each project, because they will differ. Since there are several older, larger projects which accept patches via a developer mailing list, we’ll go over an example of that now. The workflow is similar to the previous use case — you create topic branches for each patch series you work on. The difference is how you submit them to the project. Instead of forking the project and pushing to your own writable version, you generate email versions of each commit series and email them to the developer mailing list: $ git checkout -b topicA ... work ... $ git commit ... work ... $ git commit Now you have two commits that you want to send to the mailing list. You use git format-patch to generate the mbox-formatted files that you can email to the list — it turns each commit into an email message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body. The nice thing about this is that applying a patch from an email generated with format-patch preserves all the commit information properly. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch The format-patch command prints out the names of the patch files it creates. The -M switch tells Git to look for renames. The files end up looking like this: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] Add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 You can also edit these patch files to add more information for the email list that you don’t want to show up in the commit message. If you add text between the --- line and the beginning of the patch (the diff --git line), the developers can read it, but that content is ignored by the patching process. To email this to a mailing list, you can either paste the file into your email program or send it via a command-line program. Pasting the text often causes formatting issues, especially with “smarter” clients that don’t preserve newlines and other whitespace appropriately. Luckily, Git provides a tool to help you send properly formatted patches via IMAP, which may be easier for you. We’ll demonstrate how to send a patch via Gmail, which happens to be the email agent we know best; you can read detailed instructions for a number of mail programs at the end of the aforementioned Documentation/SubmittingPatches file in the Git source code. First, you need to set up the imap section in your ~/.gitconfig file. You can set each value separately with a series of git config commands, or you can add them manually, but in the end your config file should look something like this: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false If your IMAP server doesn’t use SSL, the last two lines probably aren’t necessary, and the host value will be imap:// instead of imaps:// . When that is set up, you can use git imap-send to place the patch series in the Drafts folder of the specified IMAP server: $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you’re sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off. You can also send the patches through an SMTP server. As before, you can set each value separately with a series of git config commands, or you can add them manually in the sendemail section in your ~/.gitconfig file: [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 After this is done, you can use git send-email to send your patches: $ git send-email *.patch 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Then, Git spits out a bunch of log information looking something like this for each patch you’re sending: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] Add limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Падказка For help on configuring your system and email, more tips and tricks, and a sandbox to send a trial patch via email, go to [git-send-email.io]( https://git-send-email.io/ ). Summary In this section, we covered multiple workflows, and talked about the differences between working as part of a small team on closed-source projects vs contributing to a big public project. You know to check for white-space errors before committing, and can write a great commit message. You learned how to format patches, and e-mail them to a developer mailing list. Dealing with merges was also covered in the context of the different workflows. You are now well prepared to collaborate on any project. Next, you’ll see how to work the other side of the coin: maintaining a Git project. You’ll learn how to be a benevolent dictator or integration manager. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.digitalcameraworld.com/tag/12-lenses-of-christmas | 12 lenses of Christmas Coverage | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . 12 lenses of Christmas Latest about 12 lenses of Christmas 12 lenses of Christmas: Pancake lenses! Fisheye lenses! DSLR lenses! Limited edition lenses! The freaks come out to play By Matthew Richards published 5 January 26 12 LENSES OF XMAS Canon DSLRs got a new lens, Sony refreshed its popular kit lens at long last, and we had pancakes, fisheyes and macros galore 12 LENSES OF XMAS 12 lenses of Christmas: Canon makes enough lenses to wrap around the planet, Nikon remembers that DX cameras exist By Matthew Richards published 3 January 26 12 LENSES OF XMAS TTArtisan resurrects a classic Canon lens, while smartphone makers start adding dedicated camera lenses to their handsets 12 LENSES OF XMAS 12 lenses of Christmas: Laowa and Viltrox try to outdo each other for most new lenses in the same month! By Matthew Richards published 2 January 26 12 LENSES OF XMAS Sony and OM System bring out two of their biggest guns, but third parties created mayhem with well over a dozen new lenses 12 LENSES OF XMAS 12 lenses of Christmas: Nikon redesigns a classic, while Sigma, Laowa and Viltrox work on world-first lenses By Matthew Richards published 1 January 26 12 LENSES OF XMAS Canon and Nikon finally receive a top travel zoom, Hasselblad drops a "one lens to rule them all" and Sigma reveals its mighty 200mm f/2 12 LENSES OF XMAS 12 lenses of Christmas: Sigma brings the bokeh, Fujifilm flips a pancake with a twist, and Laowa does what Canon can't By Matthew Richards published 30 December 25 12 LENSES OF XMAS Sigma throws down the gauntlet, Leica and Voigtländer reveal world-first glass, while Laowa brings back a long-lost Canon lens 12 LENSES OF XMAS 12 lenses of Christmas: China comes knocking on the door with a boatload of budget camera lenses By Matthew Richards published 29 December 25 12 LENSES OF XMAS Cheap lenses, chip lenses, commemorative retro lenses, tilt lenses… and a much maligned lens from Canon 12 LENSES OF XMAS 12 lenses of Christmas: Sony broke trinity lenses, while Canon broke the internet with a skeleton from its closet By Matthew Richards published 28 December 25 12 LENSES OF XMAS One of Sony’s announcements had all the hallmarks of an April Fools’ prank… and even more so for Canon’s "new" RF mount lens 12 LENSES OF XMAS 12 lenses of Christmas: A legendary lens maker returns while Canon debuts PZ and hybrid glass By Matthew Richards published 27 December 25 12 LENSES OF XMAS All-star team-ups take center stage, as camera manufacturers join forces, and we even get new a DSLR lens! 12 LENSES OF XMAS 12 lenses of Christmas: Nikon's Red relationship finally bears fruit, while vintage camera lenses run riot By Matthew Richards published 26 December 25 12 LENSES OF XMAS Nikon announced spectacular lenses for stills and video, Sony went little and large, and we had an A-Z moment (from Artisans to Zeiss) 12 LENSES OF XMAS 12 lenses of Christmas: Canon RF owners rejoice, as third-party lenses finally arrive! By Matthew Richards published 25 December 25 12 LENSES OF XMAS Ultra-wide lenses, ultra-slim lenses, and Canon mirrorless users get some welcome news from Sigma – January 2025 was a ball! 12 LENSES OF XMAS 1 2 3 4 5 Archives Get the Digital Camera World Newsletter The best camera deals, reviews, product advice, and unmissable photography news, direct to your inbox! Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. LATEST ARTICLES 1 Rugged phones completely changed my life in 2025 – here's why these big beasts have become my most trusted travelling companions 2 DJI Osmo Mobile 8 review: A pro-grade phone gimbal that keeps up with ambitious creators without breaking the bank 3 Is it possible to use a treadmill while editing photos? I’m a photographer – and now I’m hooked on standing desks 4 Memory card and camera phone prices are likely to rise... all thanks to AI 5 You have less than 2 weeks to enter the £10,000 LCE Photographer of the Year Digital Camera World is part of Future US Inc, an international media group and leading digital publisher. Visit our corporate site . Add as a preferred source on Google Terms and conditions Contact Future's experts Privacy policy Cookies policy Advertise with us About us Accessibility Statement Careers © Future US, Inc. Full 7th Floor, 130 West 42nd Street, New York, NY 10036. Close Please login or signup to comment Please wait... Login Sign Up | 2026-01-13T09:29:44 |
https://git-scm.com/book/id/v2/Memulai-Memasang-Git | Git - Memasang Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.5 Memulai - Memasang Git Memasang Git Sebelum Anda mulai menggunakan Git, Anda harus membuatnya tersedia pada komputer Anda. Meskipun sudah terpasang, adalah gagasan yang baik untuk memperbarui ke versi terakhir. Anda dapat memasangnya sebagai package atau melalui pemasang lainnya, atau mengunduh sumber kodenya dan meng- compile -nya sendiri. Note Buku ini ditulis menggunakan Git versi 2.0.0 . Meski begitu, kebanyakan perintah yang kita gunakan seharusnya dapat bekerja meskipun pada versi Git yang sebelumnya, beberapa dari itu mungkin tidak bekerja atau bekerja dengan sedikit berbeda jika Anda menggunakan versi yang sebelumnya. Karena Git sangat baik dalam mempertahankan kesesuaian dengan versi sebelumnya, sebarang versi setelah 2.0 seharusnya dapat bekerja dengan baik. Memasang pada Linux Jika Anda ingin memasang Git pada Linux melalui pemasang biner, umumnya Anda dapat melakukannya melalui alat pengelola paket dasar yang sudah terpasang dengan distribusi Linux Anda. Jika Anda menggunakan Fedora, misalnya, Anda dapat menggunakan yum : $ yum install git Jika Anda menggunakan distribusi berdasarkan Debian seperti Ubuntu, cobalah apt-get : $ apt-get install git Untuk pilihan lebih banyak, ada banyak arahan untuk memasang pada beberapa jenis Unix yang berbeda pada situs web Git, di http://git-scm.com/download/linux . Memasang pada Mac Ada beberapa cara untuk memasang Git pada Mac. Cara yang paling mudah adalah dengan memasang Xcode Command Line Tools. Pada Mavericks (10.9) atau yang lebih baru, Anda dapat melakukan ini hanya dengan mencoba menjalankan git dari Terminal saat pertama kali. Jika belum terpasang, dia akan memberitahu Anda untuk memasang Git. Jika Anda ingin versi yang lebih mutakhir, Anda dapat memasangnya lewat pemasang biner. Pemasang Git pada OS X dipelihara dan tersedia untuk diunduh pada situs web Git, pada http://git-scm.com/download/mac . Figure 7. Pemasang Git pada OS X. Anda juga dapat memasangnya sebagai bagian dari pemasangan GitHub untuk Mac. GUI untuk Git mereka memiliki pilihan untuk memasang peralatan command line juga. Anda dapat mengunduh alatnya dari situs web GitHub untuk Mac, pada http://mac.github.com . Pemasangan pada Windows Juga ada beberapa cara untuk memasang Git pada Windows. Bentuk resminya dapat diunduh pada situs web Git. Pergi ke http://git-scm.com/download/win dan unduhannya akan berjalan secara otomatis. Catat bahwa ini adalah proyek yang bernama Git untuk Windows (juga disebut dengan msysGit), yang terpisah dari Git itu sendiri; untuk informasi lebih lanjut, pergi ke http://msysgit.github.io/ . Cara mudah lainnya untuk memasang Git adalah dengan memasang GitHub untuk Windows. Pemasangnya menyertakan versi command line dari Git dan juga GUI-nya. Itu juga bekerja dengan baik pada Powershell, dan mengatur credential caching dengan solid dan pengaturan sane CRLF . Kita akan belajar lebih tentang hal-hal tersebut sebentar lagi, namun bisa dikatakan ini adalah yang Anda inginkan. Anda dapat mengunduh ini dari situs web GitHub untuk Windows, pada http://windows.github.com . Memasang dari Sumber Beberapa orang mungkin merasa memasang Git dari sumbernya adalah hal yang berguna, karena Anda akan mendapatkan versi yang paling mutakhir. Pemasang biner cenderung tertinggal, meski Git telah berkembang dalam beberapa tahun terakhir, hal ini tidak membuat perbedaan yang berarti. Jika Anda ingin memasang Git dari sumbernya, Anda perlu memiliki library berikut yang Git bergantung padanya: curl , zlib , openssl , expat , dan libiconv . Sebagai contoh, jika Anda berada pada sistem yang memiliki yum (seperti Fedora) atau apt-get (seperti pada sistem berdasarkan Debian), Anda dapat menggunakan salah satu dari perintah-perintah berikut untuk memasang semua ketergantungannya: $ yum install curl-devel expat-devel gettext-devel \ openssl-devel zlib-devel $ apt-get install libcurl4-gnutls-dev libexpat1-dev gettext \ libz-dev libssl-dev Ketika Anda telah memiliki ketergantungan yang dibutuhkan, Anda dapat pergi dan mengambil keluaran tarball terbaru dari beberapa tempat. Anda dapat mengambilnya lewat situs Kernel.org, pada https://www.kernel.org/pub/software/scm/git , atau dari mirror milik situs GitHub, pada https://github.com/git/git/releases . Pada umumnya nampak jelas versi apa yang paling mutakhir pada halaman GitHub, namun pada halaman kernel.org juga memiliki release signature jika Anda ingin memeriksa unduhan Anda. Kemudian, compile dan pasang: $ tar -zxf git-1.9.1.tar.gz $ cd git-1.9.1 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc install-html install-info Setelah ini selesai, Anda juca dapat mengambil Git lewat Git itu sendiri untuk pembaruan: $ git clone git://git.kernel.org/pub/scm/git/git.git prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.drupal.org/node/3251385 | Configuration Kits | Contributed module documentation | Drupal Wiki guide on Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Documentation Search Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Drupal Extending Drupal Contributed modules Contributed module documentation Advertising sustains the DA. Ads are hidden for members. Join today Contributed module documentation Active Tags A11Y Paragraphs Tabs AI AI Interpolator AI Migration API Authentication API module APITools Accelerated Mobile Pages (AMP) Access NASA API Access Policy Accessibility Scanner Acquia Migrate: Accelerate Actions UI Activity Tracker module ActivityPub Add To Calendar Date Augmenter AddToAny Share Buttons Address Decoupled Address for Luxembourg Address for Rep. of Moldova Admin Menu Swap Adobe Launch Advanced CSS/JS Aggregation Advanced Email Validation Advanced File Destination - Ho to use Advanced Insert View Advanced Varnish Advanced Views RSS Feed Aggregator Akamai Album Photos Alexa Allow a content type only once (Only One) Altcha Anu LMS Apigee API Catalog Apigee Developer Portal Kickstart Apigee Edge Apigee Monetization Apple News Astrology Atoms AudioField Audit files Augmentor User Guide Authorization Auto Link Auto Node Translate Auto Taxonomy Term Translate AutoFloat Automatic Updates Avatar Kit Azure Drupal Sync BAT Guide BEE hotel Backstop Generator Backup and Migrate Bamboo Twig Barcodes Behat UI Better Exposed Filters Bibliography & Citation BigCommerce Block Class Block Form Alter Block List Override Block Style Plugins Blog Book Boost Bootstrap Layouts Bootstrap Paragraphs Bootstrap Quick Tabs Bootstrap Theme Toggler Block Bothive Chatbot Botman Boxout Braintree Cashier Breakgen Brightcove Video Connect Bundle override Burndown Business Rules Bynder CAS CDEK API CKEditor 4 LTS CKEditor 5 Premium Features CKEditor CKEditor Accessibility Auditor CKEditor CodeMirror CKEditor Entity Link CKEditor Font Size and Family CKEditor Google Search CKEditor Libraries Group CKEditor: N1ED plugin CMRF Core Documentation CSV Importer CSV to Config Cached moderation state Calendar View Canvas LTI Captcha Keypad Changed Fields API (8.x-3.x) Changed Fields API Chaos Tool Suite (ctools) Chart Suite Guide Charts Chatbot API Chatbot Framework Claro Cloud Cloudflare Stream Cloudinary Coder Collapsiblock Color Color Field Comment Notify Comment mover Commerce Commerce API Commerce Affirm Credit Payment Gateway Commerce Approve Commerce Authorize.Net Commerce Braintree Commerce Cart API Commerce Cart Flyout Commerce DIBS integration Commerce Easy Commerce Funds Commerce Google Tag Manager Commerce Ingenico Commerce Inventory Commerce Invoice Commerce Migrate Commerce NoFraud Commerce Order Document Commerce PVT Commerce Pagseguro Transparente Commerce PayPal Commerce Payment Extra Commerce Point of Sale (POS) Commerce PostFinance Checkout Commerce Postfinance Commerce Product Options Commerce Recurring Metered Commerce Rental Commerce Reporting Commerce Square Connect Commerce Time Slots Commerce Tpay Commerce TrustedShops Commerce Variation Add-on Commerce Webform Order Commerce iATS Commerce iDEAL Payment Gateway Component Schema Components Computed Field Computed Field Plugin Conditional Fields Config Override Inspector Config Pages Config Single Export Config Token Config partial export Configuration Kits Configuration Split Content Alerts Content Feedback Content Import Content Packager Content Planner Content Synchronization Content-Security-Policy ContentAccess Create fields programmatically Crossword CrowdSec CsvtoTable Cura Childcare Suite Cura Childcare Suite Currency Custom 4XX Pages Custom API Custom Field Custom Status Report Custom Tokens Custom Tokens and its snippets Custom breadcrumbs Customerror D8 Rules Essentials Dashboard Date Augmenter API Decoupled Blocks: Vue.js Decoupled Toolbox Decoupled Toolbox Decoupled quiz Default Content for D8 Delete Entity Translations Dempo Deploy Deploying Meilisearch to production Devel Devel Generate Commerce Developer Suite Developer portal Digital Signage Framework Disclosure Menu Disclosure Menu Display Suite Chained Fields Dominican Catalogus Module DraggableViews Drupal Chatbot Drupal Commerce Merchant Warrior Drupal Contribution Drupal Diversity & Inclusion Drupal Js Path Drupal LMS Drupal OAuth & OpenID Connect Login - OAuth2 Client SSO Login Drupal OAuth OIDC Login Drupal Remote Dashboard Drupal Slider Drupal Website Security – Complete Protection for Your Site Drupal WhatsApp Drupal YouTuber Drupal driver for SQL Server and SQL Azure DubBot ECA: Event - Condition - Action ECC EU Cookie Compliance EVA Easy Breadcrumb Easy News Editor Button Link Ek Jitsi Elasticsearch Connector Email Verification / SMS Verification / OTP Verification Encrypt Entitree Administration Guide Entity Access Password Entity Browser - Table Layout Entity Browser Entity Pager Entity Parser Entity Prepopulate Entity Print Entity Reference Facet Link Entity Reference Override Entity Reference Views Entity Reference Views Select Entity Registration Entity Search Autoindex Entity Share Entity Share WebSub Entity Update Entity Usage Entity Usage Addons Entity browser Environment indicator Epsilon Harmony Connector Ethereum Evaluate Webform Event Platform Events Logger Excel Importer Exerciser Usage Expire reset password link Extensions API External Authentication External Entities External Entities Database storage Extra Block Types (EBT) Extra Paragraph Types (EPT) Facebook Instant Articles Facet Bot Blocker Facets Facets Date Range Picker Factory Lollipop Feature Toggle Features Feeds Feeds Migrate Feeds Paragraphs Feeds extensible parsers Field Encrypt Field Gallery Field Group Field Inheritance Field description tooltip Field validation File Extractor Filebrowser FillPDF Firebase Authentication Guide Fivestar Flag Flag Lists Flashpoint Education Flexible Views Flickr Integration Suite Flow2 Fluent Flysystem Focal Point Focal Point FolderShare Guide Font Awesome Icons Footnotes Form mode manager FormAlter as Plugin FormAssembly Formatter Suite Guide Formdazzle! Forms steps FortyTwo Forum module Forward Freelinking Frontend Editing Frontify Assets FullCalendar Block Funding GA Push GIT Info Report GLightbox Gatsby Integration General Data Protection Regulation Geocluster D8/D9 Set-up Geofield Geolocation Field Get Linkedin Posts Ghost Inspector Integrator Ghost Inspector Integrator Gin Toolbar Custom Menu Ginger Robot Gardens Ginger Robot Suite Give GlobalDoc’s LangXpert Connect for Drupal Googalytics Google API PHP Client Google Analytics Google Analytics Counter Google Analytics Search API Autocomplete Google Authentication for Users Google Bard Google Calendar Import Google Programmable Search Engine Gophish Integration GovUK Notify GrapesJs Editor - Page builder GraphQL Grid Widget Group Group Content Moderation Group Flex Group Invite Group Media Group Subscription Group by Field Widget Grouper Usage Gutenberg Gutenberg Content Embed Gutenberg Starter Gutenberg Starter Gutenberg USWDS Guzzle REST Generator HAL HAX HTML Mail HTML Title HTTP Client Manager Hanging Conjunctions Filter HelloSign Hidden Tab Honeypot Hospital Price Transparency Hotkeys for Save How to Configure Drupal Sharepoint Integration How to test a module locally using DDEV (Webform Booking example) Human Presence Form Protection Hux IMCE File Manager IPMA Weather Iconify Icons If Then Else Iframe Media Embed Video Image Base64 Formatter Image Optimize Image Replace Imageshop Immoweb API Client In Other Words Inline Formatter Field Insert Instagram Block Integrating Frontify with Drupal: A Comprehensive Guide Intercept Islandora JSON Field Utils JSON:API Search API Janrain Connect Juicebox HTML5 Responsive Image Galleries Juicer - Social Media Feed Aggregator Key Keycloak OpenID Connect Klaro Consent Management Knowledge Konami Code LDAP Integration LDAP Integration with Active Directory and OpenLDAP - NTLM & Kerberos Login Language Negotiation Url Matrix Layout BG Layout Builder Additions Layout Builder Block Sanitizer Layout Builder Plus Layout Builder Restrictions Layout Builder Settings Report Layout Builder Styles Layout Builder Tabs Section Layout Components Layout Options Layout Paragraphs Lazy-load Leaflet Leaflet More Markers Libraries API LiftIgniter Lightgallery Lightning Accessibility Lightweight Directory Access Protocol (LDAP) Link attributes Link icon Linkback Linkit Lndr Localist Drupal Localization server Localized Configuration Loco Translate Loqate Ludwig Lunr search Maestro Maestro Activepieces Integration Mailchimp Maintenance Manage display Managing User Account Expiration with User Expire Module Mapbox Field Markdown Markdown Easy Markdown Exporter Marketing Cloud Mask Field Matomo Analytics Maxlength Media Contextual Crop Media Gallery Media Library Form Element Media PDF Thumbnail Media Video Micromodal Media: Acquia DAM Membership Menu Manipulator Menu Migration (Import & Export) Message Message Integration Message Thread Metatag Metatag Google Scholar Micro Site Microsoft Entra ID SSO Login Microsoft Entra sync Migrate Magician Migrate QA Migrate Source CSV Migrate Source GraphQL Migrate Source JCR Migration Tools Mime Mail Mix Modal Modifiers Moodle REST Mother May I Multilanguage Form Display Multiple Registration Multistep Form Framework Multiversion NASA Astronomy Picture of the Day NFT Name Field Nbox Node Type count Notify OAuth 1.0 OAuth Server - API Documentation OAuth Server - SSO Setup Guides OAuth2 & OpenID Connect OAuth2 Client OEmbed Lazyload OH Office 365 Connector One Time Password SMS Open ReadSpeaker OpenChurch OpenEDU OpenID Connect OpenID Connect Microsoft Azure Active Directory client OpenLayersD8 OpenQuestions Openlayers Oracle Driver Oracle Eloqua API Redux OwnTracks PCO - Planning Center Online API PHP filter PNX Gallery PNX Media Packages Packagist Pagedesigner Panopoly 2 for Drupal 8/9 Paragraph Group Paragraphs Paragraphs Bundles Paragraphs Bundles Import Paragraphs Collection Paragraphs Gridstack Paragraphs Role Visibility Parameter Message Paranoia Pathauto Patternkit Performance Budget Permalink Block Permanent Entities Permissions by Term Persistent Login PhotoSwipe Place Blocks Plotly.js Graphing Plupload Poll Popup field group Postoffice Potion Preprocessor Files Preprocessor Plugins Preview graph QL Private DNS Private Message Progressive Web App (PWA) Project Browser Protected Content Pusher API Quadstat Quick Edit Quick Node Clone Quickchat Quicklink RDF RELAXed Web Services RNG Rabbit MQ Radioactivity Range Slider Reactify theme & module Read time Recipes Cookbook Recombee Recurring Dates Field Recurring Events RegEx Field Validation Registration Confirm Email Address Registration codes Registration role Release Version Remote Stream Wrapper Responsive Background Image Responsive Class Field Responsive Image Formatter Tools (RIFT) Responsive Image Preload Responsive Tables Filter Responsive menu Rocket.Chat Integration Module Guide Role paywall Rules Rules API POST SAML Authentication SAML IDP 2.0 Single Sign On (SSO) - SAML Identity Provider SAML SP Single Sign On (SSO) - SAML Service Provider - by Miniorange SMS Framework SMS System SVG Image Field Salesforce ECA Integration Salesforce MFW Salesforce Suite Scheduled Transitions Scheduled Updates Scheduler Schema.org Blueprints Schema.org Metatag Search 404 Search API Search API AI Search API Autocomplete Search API Decoupled Search API Exclude Entity Search API Federated Solr Search API RediSearch Search API Sajari Search API Solr Search API Xunsearch Search API opensolr Search and Replace Scanner SearchStax Search API Select 2 Semantic Views Sender Service Worker Registration Setting up the Release Version module Shared Field Display Settings Sharerich Sherpa Webform ShrinkTheWeb Simple Content Notifications Simple Decoupled Preview Simple FB Connect Simple Instagram Feed Simple Node Importer Simple Page Manager Simple Popup Blocks Simple XML sitemap Simple multi step form Simplenews Single Content Sync Site Module Siteimprove Sitemap Sites Skilling Skins Skosmos Feeds Smart Content Overview Smart Date Smart Title Smart Trim Snippet manager Social API Social Auth Vipps Social Media Platforms Social Migration Social Post Facebook Socialfeed Socialfeed Songkick Sound Management Spectra Analytics Srijan theme Static Node Generator - How to use and Use cases Statistical Spam Filter Statistics Step by step guides to configure various 2FA / MFA / TFA methods Stop Administrator Login String Structure Sync Style Selector Style Switcher Styled Google Map Subgroup Summit Meeting List Superfish Drop-down Menus Swagger UI Field Formatter Swiper Formatter Switches Symfony Mailer Syncer Synonyms System Monitor TMGMT Capita TMGMT Plunet TacJS Tagify Targets Taxonomy Bulk Actions (TBA) Tealium iQ Tag Management Telephone International Widget Template Entities Template Whisperer TextRazor - Automatic text classification The Better Mega Menu Time's Up Token Token Filter Tom Select Tombstones Tone Toolshed Tooltip Tour Transaction Transform API Translation Management Tool Trending Topics Tweet Feed Twig Components Twig Render This Twig Tools Twig tweak Twitter API Block Twitter Tweets Typed Data API Enhancements UI Patterns UI Patterns Pattern Lab UI Styles URL Embed Ubercart Uikit Slideshow Ultimate table Field UniOne Unisender newsletter UpTime Widget Upload File History User CSV Import User Guide for Field Encrypted Searchable - FES User History User Session Management and Monitoring Using CAT tools for Drupal Varbase Editor Varnish purger Vertex AI Search Vertex AI Search Promoted Results Video Video Embed Field Video Toolbox View Transitions Views Add Button Views Bootstrap for Bootstrap 3 Views Bootstrap for Bootstrap 5 Views Bootstrap for Bootstrap4 Views Bulk Operations (VBO) Views Display Union Views Field View Views Local Tasks Views Mobile Views PDF Views RSS: Media (MRSS) Elements Views Reference Field Views Regex Functions Views Remote Data Views Send Views Slideshow Views TimelineJS Views filter content type Vipps Recurring Payments: Installation Visitors Visual Layout Suite Visual Website Optimizer VisualN Visualization Charts Vite Voting API Reaction Wallee Warden Wayfinding Web Page Archive Web Service Data Webform Webform Attachment Gated Download Webform Eloqua Webform GoogleSheets Webform Trello Webform Workflows Element Website Feedback When and why to use Link Param Propagator WissKI WordPress Migrate Wordcount Workbench Menu Access Workflow Workout Usage Workout Usage with Drush Workspace XML Sitemap XML-RPC Xero Sync YAML Content YAML To PHP Youtube Gallery Zoom API agGrid ePayco integration htmLawed HTML filter/purifier memoQ translation miniOrange User Provisioning reCaptcha v3 signageOS simplytest.me Token Configuration Kits Configuration kits are made to make life easier for site builders and module maintainers. This guide will help you use, extend, and create your own configuration kits. Create Your Own Configuration Kit How to export configuration and make your own reusable module Related Content Configuration Kits This project is meant as central registry for modules that act as a configuration kit, or include one or more as a submodule. Guide maintainers Drupal’s online documentation is © 2000-2026 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0 . PHP code is distributed under the GNU General Public License . Infrastructure management for Drupal.org provided by Need a Drupal 7 extended support partner? Consider Tag1. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:44 |
https://www.atlassian.com/ko/software/jira/service-management/resources | Jira Service Management 리소스 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 솔루션 사용 사례별 기능별 업계별 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 Back 가격 리소스 유형별 ITSM 제품 가이드 템플릿 추가 리소스 Back 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Jira Service Management는 이제 Service Collection의 일부가 되어 그 어느 때보다 강력해졌습니다. Rovo, 자산 및 새로운 Customer Service Management 앱으로 탁월한 서비스 경험을 제공하세요. 지금 사용해 보세요 Jira Service Management 리소스 라이브러리 최신 IT 서비스 관리의 기능 활용하기 주요 리소스 분석 보고서 The Forrester Wave TM : ESM, 2023에서 리더로 선정된 Atlassian 자세히 알아보기 비디오 Jira Service Management 주간 데모 자세히 알아보기 가이드 Jira Service Management 시작하기 자세히 알아보기 필터 | 초기화 형식 모든 형식 백서 및 전자책 분석 보고서 제품 가이드 사례 연구 제품 데모 아티클 동영상 및 웹 세미나 데이터시트 제품 업데이트 업계 보고서 토픽 모든 주제 자산 및 구성 관리 변경 관리 고객 서비스 관리 DevOps 엔터프라이즈 서비스 관리 인시던트 관리 ITSM Jira Service Management 서비스 요청 소식 스토리 / 필터 형식 모든 형식 모든 형식 백서 및 전자책 분석 보고서 제품 가이드 사례 연구 제품 데모 아티클 동영상 및 웹 세미나 데이터시트 제품 업데이트 업계 보고서 토픽 모든 주제 모든 주제 자산 및 구성 관리 변경 관리 고객 서비스 관리 DevOps 엔터프라이즈 서비스 관리 인시던트 관리 ITSM Jira Service Management 서비스 요청 소식 초기화 0 결과 × 가입하여 더 많은 문서와 자습서를 보세요. Thank you for subscribing 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://www.atlassian.com/ja/software/jira/templates/it-operations | IT 運用テンプレート | Jira テンプレート・ライブラリ | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で入手する 機能 すべての機能 Jira の Rovo Back ソリューション チーム ユースケース 企業規模 チーム マーケティング エンジニアリング デザイン オペレーション IT ユースケース はじめに 計画 キャンペーン管理 アジャイルプロジェクト管理 プログラム管理 企業規模 Enterprise Back 製品ガイド テンプレート テンプレート すべてのテンプレート ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス Jira Service Management のテンプレート Back 価格 その他 + 表示を減らす - 無料で入手する Back 無料で入手する Jira テンプレート Open and close the navigation menu カテゴリー ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス プロジェクト管理テンプレート 無料で入手する カテゴリー ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス プロジェクト管理テンプレート IT 運用テンプレート 運用マネージャー、開発者、サイト信頼性エンジニアを Jira Service Management でつなげます。チームが変更に関する状況を完全に把握し、インシデント発生時にチーム一丸となって解決できるようにします。 IT サービス管理 リクエストを取り込み、アラートを設定し、インシデントを登録して、課題を迅速に解決します。 高度な IT サービス管理 ITSM のベスト・プラクティスによりインシデント、変更、問題を管理します。 カスタマー サービス管理 外部顧客に優れたサービス・エクスペリエンスを提供します。 分析サービス管理 従業員が必要とするデータやインサイトに関するリクエストを管理します。 成功しているチームは IT 運用テンプレートを使用しています 「整頓されたワークフローや、Jira Service Management とその他の製品との統合によって、エンジニアの負荷が大きく軽減されました。疲労度も減り、仕事を前よりも楽しんでいます」 Roman Bugaev 最高技術責任者、Flo IT 運用リソース IT 運用のための Jira Service Management ソフトウェア開発と IT を同じプラットフォームにまとめて、サービスを提供および管理する使いやすいソリューションです。 詳細を見る Jira Service Management 製品ガイド Jira Service Management の使用方法：ガイド、チュートリアルとデモ ガイドを確認する Jira Service Management デモ 関心をお持ちの特定の機能を選択してください。デモをカスタマイズできます。 デモを見る 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://git-scm.com/book/sv/v2/Grunder-i-Git-Sammanfattning | Git - Sammanfattning About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.8 Grunder i Git - Sammanfattning Sammanfattning Nu kan du göra alla grundläggande lokala Gitoperationer — skapa eller klona ett förvar, göra ändringar, preparera och spara ändrigarna samt visa historiken av alla ändrigana som sparats i förvaret. Nu är det dags att gå igenom Gits kanske kraftfullaste funktion: förgreningar. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/uk/v2/%d0%a0%d0%be%d0%b7%d0%bf%d0%be%d0%b4%d1%96%d0%bb%d0%b5%d0%bd%d0%b8%d0%b9-Git-%d0%92%d0%bd%d0%b5%d1%81%d0%b5%d0%bd%d0%bd%d1%8f-%d0%b7%d0%bc%d1%96%d0%bd-%d0%b4%d0%be-%d0%bf%d1%80%d0%be%d0%b5%d0%ba%d1%82%d1%83 | Git - Внесення змін до проекту About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 5.2 Розподілений Git - Внесення змін до проекту Внесення змін до проекту Дуже складно описати як зробити внесок до проекту, через те, що існує неосяжна кількість варіантів того, як це робиться. Оскільки Git дуже гнучкий, люди можуть співпрацювати різноманітними методами, і дуже проблематично описати, як вам слід робити внесок — кожен проект трохи своєрідний. Ось деякі зі змінних, що впливають на це: кількість активних учасників, вибраний процес роботи, чи є у вас доступ на запис, та можливо метод внеску ззовні. Перша змінна — кількість активних учасників — скільки користувачів активно роблять внески коду до проекту, та як часто? У багатьох випадках, у вас буде два або три розробника з декількома комітами на день, чи навіть менше для дещо неактивних проектів. Для більших компаній чи проектів, кількість розробників може вимірюватись тисячами, з сотнями або тисячами комітів щодня. Це важливо, адже зі збільшенням кількості розробників, виникає все більше проблем з тим, щоб переконатись, що код правильно застосовується та може бути легко злитим. Зміни, які ви надсилаєте, можуть виявитись застарілими, або геть зламаними роботою, яка була злита, доки ви працювали або доки ваші зміни очікували на схвалення та застосування. Як ви можете зберігати ваш код постійно оновленим, а коміти правильними? Наступною змінною є те, який процес роботи використовується в проекті. Він централізований, та кожен розробник має рівне право запису до головної лінії коду? Чи є в проекті супроводжувач чи менеджер інтеграції, який перевіряє всі латки (patch)? Чи всі латки перевіряються іншими та схвалюються? Чи ви приймаєте участь в цьому процесі? Чи може використовується система лейтенантів, і необхідно спочатку надіслати свою роботу до них? Наступним питанням є ваш доступ до проекту. Необхідний процес роботи для внеску до проекту є дуже відмінним в залежності від того, чи маєте ви доступ на запис до проекту, чи ні. Якщо у вас немає доступу на запис, як проект воліє приймати вашу роботу? Чи є в нього хоча б якісь правила? Скільки роботи ви збираєтесь надсилати за раз? Як часто ви будете це робити? Усі ці питання можуть вплинути на те, як робити внесок до проекту ефективно та які процеси роботи є ліпшими чи доступними вам. Ми розглянемо деталі кожного з них у набір прикладів використання, від простого до складніших; ви маєте бути в змозі створювати специфічні процеси роботи, які вам потрібні на практиці, з цих прикладів. Правила щодо комітів До того, як розпочати з конкретних прикладів використання, наведемо коротеньку нотатку про повідомлення комітів. Мати добрі правила щодо створення комітів та дотримування їх робить працю з Git та співпрацю з іншими набагато легшою. Проект Git постачає документ, що викладає чимало гарних порад щодо створення комітів, з яких надсилати латки — ви можете прочитати їх у вихідному коді у файлі Documentation/SubmittingPatches . По-перше, у ваших змінах не має бути помилок пробільних символів. Git надає легкий спосіб перевірити це — перед тим, як створювати коміт, виконайте git diff --check , що знаходить можливі помилки з пробільними символами та надає їх список для вас. Рисунок 56. Вивід git diff --check . Якщо виконати цю команду перед створенням коміту, то можна дізнатись, чи будуть проблеми з пробільними символами в цьому коміті, які можуть дратувати інших розробників. По-друге, намагайтесь робити кожен коміт логічно окремим набором змін. Якщо можете, спробуйте робити ваші зміни легкими для сприйняття — не працюйте всі вихідні над пʼятьма різними завданнями та потім створюйте з них усіх один величезний коміт у понеділок. Навіть якщо ви не робили комітів впродовж вихідних, скористайтесь індексом у понеділок щоб розділити свою роботу принаймні на один коміт для кожного завдання, зі змістовним повідомленням кожного коміту. Якщо деякі зміни редагують один файл, спробуйте використати git add --patch , щоб частково проіндексувати файли (розглянуто докладно в Інтерактивне індексування ). Відбиток проекту наприкінці гілки однаковий, хоч ви зробите один коміт, хоч пʼять, доки всі зміни додані в якийсь момент, отже спробуйте спростити своїм колегам розробникам перегляд ваших змін. Цей підхід також сприяє легшому вилученню чи вивертанню (revert) змін, якщо це буде потрібно пізніше. Переписування історії описує чимало корисних хитрощів Git для переписування історії та інтерактивного індексування файлів — використовуйте ці інструменти для виготовлення чистої та зрозумілої історії перед тим, як надсилати вашу роботу іншим. Нарешті, не варто забувати про повідомлення комітів. Якщо взяти за звичку створювати якісні повідомлення комітів, то використання та співпраця з Git стає значно легшою. За загальним правилом, повідомлення мають починатися з єдиного рядка, який містить не більш ніж приблизно 50 символів та описує набір змін змістовно, після якого є порожній рядок, за яким іде більш докладне пояснення. Проект Git вимагає, щоб докладніше пояснення включало мотивацію зміни та описувало різницю з попередньою поведінкою — це правило варте наслідування. Також слушно використовувати доконаний вид теперішнього часу в цих повідомленнях. Іншими словами, використовуйте команди. Замість Я додав тести для'' чи Додаю тести для,'' використовуйте ``Додати тести для.'' Ось шаблон, автором якого є Тім Поуп : Стислий (50 символів або менше) підсумок змін Докладніший пояснювальний текст, якщо потрібно. Розбивайте рядки по приблизно 72 символи. У деяких ситуаціях, перший рядок сприймається як заголовок електронного листа, а решта як текст тіла листа. Порожній рядок відділяє підсумок від тіла і є необхідним (хіба ви взагалі не пишете тіло); такі інструменти як перебазування можуть заплутатися, порожнього рядка не буде. Подальші параграфи йдуть після порожнього рядка. - Маркери елементів списку теж можна використовувати. - Зазвичай як маркер використовують дефіс або зірочку, перед якими є єдиний пробіл, з порожніми рядками між елементами, проте домовленості щодо цього різняться Якщо ваші повідомлення комітів відповідають цьому шаблонові, то всім, хто працює над проектом, буде значно легше співпрацювати. Проект Git має добре оформлені повідомлення комітів — спробуйте виконати для нього git log --no-merges , і побачите, як виглядає історія відформатованих комітів проекту. Зауваження Робіть як ми кажемо, а не як ми робимо. For the sake of brevity, many of the examples in this book don’t have nicely-formatted commit messages like this; instead, we simply use the -m option to git commit . Заради стислості, в багатьох прикладах цієї книжки повідомлення комітів будуть оформлені не так добре; натомість ми просто використовуватимемо опцію -m команди git commit . In short, do as we say, not as we do. Тобто робіть як ми кажемо, а не як ми робимо. Маленька закрита команда Найпростіший випадок, який ви можете зустріти — це закритий проект з одним чи двома іншими розробниками. ``Закритий,'' у цьому контексті, означає зі закритим вихідним кодом — недоступним зовнішньому світу. Ви та інші розробники всі мають доступ на запис до репозиторія. У такому середовищі, ви можете працювати за процесом роботи, схожим на той, за яким ви могли працювали при користуванні Subversion чи іншої централізованої системи. Ви все одно отримуєте такі переваги, як створення комітів поза мережею та неймовірно простіше галуження та зливання, проте процес роботи може бути дуже схожим: головною відмінністю є те, що зливання здійснюються на клієнті, а не на сервері під час створення коміту. Погляньмо, як це працює, коли два розробника починають працювати разом над спільним сховищем. Перший розробник, Джон, клонує репозиторій, робить зміни й створює коміти локально. (Повідомлення протоколу замінені на … у цих прикладах, щоб дещо скоротити їх.) # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'remove invalid default value' [master 738ee87] remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) Друга розробниця, Джесіка, робить те саме — клонує сховище та створює коміт зі змінами: # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Тепер, Джесіка надсилає свою працю до сервера, і тут не виникає жодних помилок: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master Останній рядок цього виводу є доволі корисним повідомленням від операції push . Основний формат — <старе-посилання>..<нове-посилання> посилання-від → посилання-до , де посилання-від позначає локальне посилання, що надсилається, а посилання-до — назва віддаленого посилання, що оновлюється. Ви зустрічатимете такі рядки далі в дискусіях, тому загальне розуміння допоможе розібратися, в якому стані різноманітні сховища. More details are available in the documentation for Докладніше про це в документації git-push . Повертаємося до нашого прикладу: невдовзі Джон щось змінює, зберігає ці зміни в локальному сховищі та намагається надіслати їх до того ж серверу: # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' Цього разу операція завершується помилкою через те, що Джесіка вже надіслала власні зміни. Це особливо важливо зрозуміти, якщо ви звикли до Subversion, оскільки ви помітите, що два розробники не редагували один і той самий файл. Хоча Subversion автоматично робить таке злиття на сервері, якщо різні файли були редаговані, у Git ви змушені спочатку зливати коміти локально. Іншими словами, Джон має спочатку отримати зміни Джесіки та злити їх разом у своєму локальному сховищі, і лише після цього йому буде дозволено їх надіслати. Як перший крок, Джон отримує працю Джесіки (лише отримує , ще не зливає з власними змінами): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master Наразі, локальне сховище Джона виглядає приблизно так: Рисунок 57. Історія Джона, що розбіглася. Тепер Джон може злити щойно отриману роботу Джесіки з власною локальною: $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Якщо локальне злиття проходить без проблем, то оновлена історія матиме такий вигляд: Рисунок 58. Репозиторій Джона після зливання origin/master . Тепер Джонові, можливо, варто запустити тести й переконатися, що зміни Джесіки не вплинули на його власні. Якщо все гаразд, він нарешті може надіслати щойно злиту роботу до серверу: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master Після цього історія комітів Джона матиме такий вигляд: Рисунок 59. Історія Джона після надсилання до сервера origin . Тим часом, Джесіка створила тематичну гілку під назвою issue54 та створила в ній три коміти. Вона не отримувала зміни Джона покищо, отже її історія комітів виглядає так: Рисунок 60. Тематична гілка Джесіки. Раптом Джесіка дізнається, що Джон надіслав до сервера щось нове, і вона хоче на це поглянути, тож вона отримує всі нові дані з сервера, яких у неї ще немає: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master Це стягує роботу Джона, яку він встиг надіслати. Історія Джесіки тепер виглядає так: Рисунок 61. Історія Джесіки після отримання змін Джона. Джесіка вважає, що її тематична гілка готова, проте бажає знати, яку частину отриманих змін Джона їй доведеться зливати зі своєю роботою, щоб мати можливість надіслати зміни. Вона виконує git log , щоб дізнатися: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 remove invalid default value Синтаксис issue54..origin/master є фільтром журналу, який просить Git відображати лише ті коміти з другої гілки (у цьому випадку origin/master ), яких немає в першій гілці (у цьому випадку issue54 ). Ми розглянемо цей синтаксис докладно в Інтервали комітів . З цього виводу можна побачити, що існує єдиний коміт, який створив Джон, та Джесіка ще не злила зі своїми локальними змінами. Якщо вона зіллє origin/master , це єдиний коміт, який змінить її локальну працю. Тепер, Джесіка може злити її тематичну працю до своєї гілки master, зливає роботу Джона ( origin/master ) до гілки master , а потім надсилає зміни назад до сервера знову. Спершу (після того, як зберегти всі зміни в комітах у тематичній гілці issue54 ), вона переходить назад до своєї гілки master , щоб підготуватися до інтеграції: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Джесіка може злити спочатку хоч origin/master , хоч issue54 — вони обидві готові, отже порядок не є важливим. Відбиток у результаті буде однаковим незалежно від порядку, який вона вибере; лише історія буде трохи різною. Вона вирішує злити спочатку гілку issue54 : $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) Жодні проблеми не трапляються; як бачите, це просте злиття перемотуванням вперед (fast-forward). Тепер Джесіка pавершує локальне злиття: зливає вже отриману роботу Джона, що чекає в гілці origin/master : $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Усе зливається чисто, і тепер історія Джесіки має такий вигляд: Рисунок 62. Історія Джесіки після зливання змін Джона. Тепер origin/master є досяжним з гілки master Джесіки, отже вона має бути в змозі успішно надіслати зміни (припускаючи, що Джон тим часом не надіслав ще якихось змін): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Кожен розробник створив декілька комітів та успішно зливав роботу іншого. Рисунок 63. Історія Джесіки після надсилання змін назад до сервера. Це один з найпростіших процесів роботи. Ви працюєте деякий час (зазвичай, переважно у тематичній гілці) та зливаєте цю працю до своєї гілки master , коли все готово. Коли ви бажаєте надати доступ до своєї роботи, треба отримати (fetch) та злити до вашого master гілку origin/master , якщо вона змінилася, та нарешті надіслати гілку master до сервера. Загальна послідовність виглядає приблизно так: Рисунок 64. Загальна послідовність подій для простого процесу роботи декількох розробників з Git. Закрита керована команда У цьому наступному варіанті, подивимось на ролі учасників у більшій закритій групі. Ви дізнаєтесь, як працювати в середовищі, де невеличка група співпрацює над функціоналом, а потім їхні командні внески інтегруються кимось іншим. Скажімо, Джон та Джесіка працюють разом над однією функцією (назвімо це featureA''), у той час як Джесіка з Джосі (це третій розробник) працюють над іншою (скажімо, featureB''). У цьому випадку, компанія використовує різновид процесу роботи з менеджером інтеграції, в якому праця окремих груп інтегрується виключно окремими інженерами, і гілка master головного сховища може бути оновленою лише цими інженерами. У цьому сценарії, вся праця відбувається у командних гілках, а пізніше стягується разом інтеграторами. Прослідкуймо за процесом роботи Джесіки, адже вона працює над двома функціями та паралельно співпрацює з двома розробниками в цьому середовищі. Припускаючи, що вона вже створила клон репозиторія, вона вирішує спочатку працювати над featureA . Вона створює нову гілку для цієї функції та щось в ній робить: # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) Тепер їй треба поділитись своєю роботою з Джоном, отже вона надсилає коміти своєї гілки featureA до сервера. Джесіка не має доступу на запис до гілки master — він є лише в інтеграторів — отже вона має надсилати до іншої гілки, щоб співпрацювати з Джоном: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Джесіка пише листа Джону, щоб повідомити про створену нею гілку featureA з її роботою, і тепер він може переглянути її. Доки вона чекає на відгук від Джона, Джесіка вирішує розпочати працю над featureB разом з Джосі. Спочатку, вона створює нову функціональну гілку, засновану на гілці master з сервера: # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Тепер, Джесіка робить декілька комітів у гілці featureB : $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Сховище Джесіки тепер має такий вигляд: Рисунок 65. Початкова історія комітів Джесіки. Вона готова надсилати свою роботу, проте отримує листа від Джосі про те, що гілка з розпочатою роботою над `featureB'' вже надіслана до сервера з ім’ям `featureBee . Джесіка має злити ці зміни зі своїми, щоб мати змогу надіслати до сервера. Спочатку Джесіка здобуває зміни Джосі за допомогою git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Якщо Джесіка досі на гілці featureB , то вона тепер може злити зміни Джосі в цю гілку за допомогою git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) Тепер Джесіка хоче надіслати свою злиту роботу над `featureB'' назад до сервера, проте вона не хоче просто надсилати свою гілку `featureB . Натомість, оскільки Джосі вже створила на сервері гілку featureBee , Джесіка хоче надіслати зміни до цієї гілки, що вона й робить командою: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee Це називається специфікація посилань (refspec). Дивіться Специфікація посилань (refspec) задля докладнішої дискусії про визпоси Git та різноманітні речі, які з ними можна робити. Також зверніть увагу на опцію -u ; це скорочення для --set-upstream , яка налаштовує гілки для легшого подальшого надсилання та отримання змін. Раптом Джесіка отримує листа від Джона про те, що він надіслав деякі зміни до гілки featureA , над якою вони працюють разом, та просить Джесіку подивитися на них. Джесіка знову виконує простий git fetch , щоб отримати всі нові дані з серверу, включно з (звісно) останніми змінами Джона: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Джесіка може продивитися журнал змін Джона, порівнявши щойно отриману гілку featureA зі своєю локальною копією тієї ж гілки: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 Якщо Джесиці до вподоби те, що вона бачить, то вона може злити нові зміни Джона до локальної гілки featureA за допомогою: $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Нарешті, Джесіка може захотіти внести кілька невеличких змін у злиті файли, тож вона може зробити ці зміни, зберегти їх у коміт в гілці featureA та надіслати кінцевий результат назад до серверу. $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Історія комітів Джесіки тепер виглядає так: Рисунок 66. Історія Джесіки після створення комітів у функціональних гілках. Якось Джесіка, Джосі та Джон повідомляють інтеграторів, що гілки featureA та featureBee на сервері готові для інтеграції до стрижневої гілки. Після того, як інтегратори зіллють ці гілки до стрижневої, отримання змін додасть новий коміт злиття, що зробить історію такою: Рисунок 67. Історія Джесіки після зливання обох її тематичних гілок. Чимало груп переходять на Git через цю можливість декільком командам паралельно працювати, та зливати різні лінії роботи пізніше. Здатність менших підгруп команди співпрацювати за допомогою віддалених гілок без необхідності залучати чи затримувати всю команду є великою перевагою Git. Послідовність для процесу роботи, який ви бачили тут, виглядає приблизно так: Рисунок 68. Базова послідовність цього процесу роботи керованої команди. Відкритий проект з форками Внески до відкритих проектів роблять дещо інакше. Оскільки у вас немає права оновлювати гілки проекту напряму, ви маєте доправити свої зміни до супроводжувачів іншим чином. Перший приклад описує внески за допомогою форків на хостах Git, які підтримують легке створення форків. Багато сайтів розгортання підтримують це (включно з GitHub, BitBucket, repo.or.cz тощо), та багато супроводжувачів проектів очікують внесків у такому вигляді. Наступна секція розгляне проекти, які бажають приймати внески латками (patches) через електронну пошту. Спочатку, ви вірогідно забажаєте створити клон головного сховища, створити тематичну гілку для латки чи низки латок, які ви плануєте внести, та попрацювати там. Ось базова послідовність для цього: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Зауваження Можливо, ви забажаєте використати rebase -i , щоб зчавити (squash) свою працю до єдиного коміту, або переставити коміти, щоб супроводжувачу було легше переглянути латку — дивіться Переписування історії задля детальнішої інформації про інтерактивне перебазування. Коли ваша робота в гілці завершена, і ви готові направити внесок до супроводжувачів, перейдіть до сторінки оригінального проекту та натисніть кнопку `Форк'', що створить ваш власний форк проекту, в який ви маєте право писати. Потім вам потрібно додати URL цього сховища як нове віддалене сховище до вашого локального репозиторію; у цьому прикладі, назвімо його `myfork : $ git remote add myfork <url> Потім треба надіслати свої зміни до цього сховища. Найлегше надіслати тематичну гілку, над якою ви працюєте, до вашого форку замість того, щоб зливати до вашої гілки master та надсилати її. Так краще, адже якщо вашу роботу не приймуть, або її висмикнуть (cherry pick), то не доведеться перемотувати гілку master (докладніше про операцію Git cherry-pick див. Процеси роботи з перебазуванням та висмикуванням ). Якщо супроводжувачі зіллють, перебазують або висмикнуть вашу працю, ви зрештою отримаєте її при отриманні з їхнього сховища в будь-якому разі. Хай там як, ви можете надіслати свою працю за допомогою: $ git push -u myfork featureA Коли ваша робота надіслана до вашого форку, потрібно повідомити супроводжувачів оригінального проекту, що ви хотіли б, щоб вони злили ці зміни. Це, зазвичай, називають pull request , і, зазвичай, ви можете або згенерувати його за допомогою сайту — GitHub має власний механізм `Pull Request'', який ми розглянемо в GitHub — або можете виконати команду `git request-pull та надіслати її вивід поштою до супроводжувачів проекту вручну. Команда git request-pull бере базову гілку, до якої ви бажаєте злити тематичну гілку, та URL Git сховища, з якого вони можуть отримати гілку, та виводить стислий опис всіх змін, які ви просите злити. Наприклад, якщо Джесіка бажає надіслати Джонові pull request та вона зробила два коміти в тематичній гілці, які вона щойно надіслала, вона може виконати це: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): added a new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Цей вивід можна надіслати супроводжувачу — у ньому повідомляється, звідки робота відгалузилась, підбиває підсумки комітів та звідки можна отримати ці зміни. У проекті, в якому ви не є супроводжувачем, зазвичай легше, щоб гілка master завжди слідкувала за origin/master , та працювати в тематичних гілках, які можна легко скасувати, якщо їх відкинули. Ще однією перевагою ізолювання напрямків роботи в тематичних гілках є те, що це полегшує перебазування вашої праці, якщо вершина головного сховища пересунулась за цей час та ваші коміти більше не застосовуються чисто. Наприклад, якщо ви бажаєте подати на розгляд другу тему до проекту, не продовжуйте працювати в щойно надісланій тематичній гілці — почніть спочатку з гілки master головного сховища. $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Тепер, кожна з ваших тем міститься в зерносховищі — щось схоже на чергу латок — їх можна переписувати, перебазовувати, змінювати без взаємних завад чи залежностей, наприклад: Рисунок 69. Початкова історія комітів з роботою featureB . Скажімо, супроводжувач проекту отримав купу інших латок та спробували вашу першу гілку, проте вона вже не зливається чисто. У цьому випадку, ви можете спробувати перебазувати цю гілку поверху origin/master , розв’язати конфлікти для супроводжувачів, та надати свої зміни знову: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA Це переписує вашу історію, і тепер вона виглядає як Історія комітів після праці в featureA . . Рисунок 70. Історія комітів після праці в featureA . Оскільки ви перебазували гілку, доводиться задати -f до команди push, щоб замінити гілку featureA на сервері комітом, який не є її нащадком. Альтернативно, можна було надіслати цю нову працю до іншої гілки на сервері (можливо названу featureAv2 ). Подивімося на ще один можливий сценарій: супроводжувач подивився на роботу в другій гілці та схвалює концепцію, проте бажає, щоб ви змінили якусь окрему річ у реалізації. Ви також скористаєтесь цією можливістю, щоб перебазувати роботу на поточній гілці master . Ви починаєте з нової гілки, відгалуженої від origin/master , зчавлюєте в ній зміни featureB , розв’язуєте конфлікти, робите зміну в реалізації, та потім надсилаєте зміни назад як нову гілку: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 Опція --squash бере всю роботу з гілки, яку зливають, та зчавлює її в один набір змін, в результаті отримуємо стан репозиторія, ніби справжнє злиття сталося проте без власне створення коміту злиття. Це означає, що майбутні коміти матимуть лише одного батька, та дозволяє додати всі зміни з іншої гілки, а потім зробити ще деякі зміни до запису нового коміту. Також опція --no-commit може бути корисною, щоб відкласти коміт злиття в разі типового процесу зливання. Тепер ви можете повідомити супроводжувача про те, що ви зробили доручені зміни, т� | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%98%d0%b7%d0%b1%d0%be%d1%80-%d0%bd%d0%b0-%d0%ba%d1%8a%d0%bc%d0%b8%d1%82%d0%b8 | Git - Избор на къмити About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.1 Git инструменти - Избор на къмити Дотук научихте за повечето ежедневни команди и работни похвати, от които имате нужда в управлението и поддръжката на Git хранилище. Овладяхте основните начини за проследяване и къмитване на файлове, за манипулация на индексната област и ползата от topic клоновете и сливането. Сега ще разгледаме множество полезни трикове на Git, които може и да не ползвате често в ежедневната работа, но могат да се окажат полезни в един момент. Избор на къмити Git позволява да се обръщате към единичен къмит, серия или множество от къмити по няколко начина. Те не са непременно очевидни, но е полезно да се знаят. Единични къмити Очевидно можете да се обърнете към единичен къмит по неговия пълен, 40-символен SHA-1 хеш, но съществуват и по-лесни начини за това. Тази секция представя няколко такива. Скъсен SHA-1 Git е достатъчно гъвкав да определи кой къмит имате предвид, ако укажете първите няколко символа от хеша, стига да подадете поне 4-символен, недвусмислен стринг. Това значи, че в базата данни с обектите няма друг такъв, който да започва със същия префикс. Например, за да изследвате специфичен къмит, в който знаете че сте добавили дадена функционалност, бихте могли първо да изпълните git log , за да го намерите: $ git log commit 734713bc047d87bf7eac9674765ae793478c50d3 Author: Scott Chacon <schacon@gmail.com> Date: Fri Jan 2 18:32:33 2009 -0800 Fix refs handling, add gc auto, update tests commit d921970aadf03b3cf0e71becdaab3147ba71cdef Merge: 1c002dd... 35cfb2b... Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' commit 1c002dd4b536e7479fe34593e72e6c6c1819e53b Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 14:58:32 2008 -0800 Add some blame and merge stuff В този случай, нека кажем, че се интересувате от къмита, чийто хеш започва с 1c002dd… . Можете да инспектирате къмита с всеки от следните варианти на git show : $ git show 1c002dd4b536e7479fe34593e72e6c6c1819e53b $ git show 1c002dd4b536e7479f $ git show 1c002d Git може да установи късите, уникални абревиатури на вашите SHA-1 стойности. Ако подадете опцията --abbrev-commit към git log , ще бъдат отпечатани съкратените версии; по подразбиране Git използва седем символа: $ git log --abbrev-commit --pretty=oneline ca82a6d Change the version number 085bb3b Remove unnecessary test code a11bef0 Initial commit В общи линии, 8 до 10 символа са повече от достатъчни за гарантирана уникалност в рамките на един проект. Например, към февруари 2019, Linux ядрото (доста мащабен проект) има над 875 хиляди къмита и почти 7 милиона обекта, като не съществуват два такива с повтарящи се първи 12 символа в своя SHA-1 хеш. Забележка КРАТКО УТОЧНЕНИЕ ЗА SHA-1 Много хора се притесняват, че в даден момент, по случайност биха могли да имат два отделни обекта в едно хранилище с една и съща SHA-1 стойност. Какво следва тогава? Ако се случи да къмитнете обект, който да има същия SHA-1 хеш като предишен, различен такъв в хранилището, Git ще види предишния обект в базата данни, ще приеме че той вече е бил записан и просто ще го използва наново. Ако се опитате да извлечете този обект наново в даден момент, винаги получавате данните от първия обект. Обаче, трябва да сте наясно колко супер малко вероятно е това. SHA-1 хеш сумата е с дължина 20 байта или 160 бита. Броят на случайно хешираните обекти, необходими за осигуряване на 50% вероятност от единично повторение е приблизително 2 80 (формулата за определяне на вероятност за конфликт е p = (n(n-1)/2) * (1/2^160)) . 2 80 е 1.2 x 10 24 или 1 милион милиарда милиарда. Това е 1200 пъти по-голямо число от броя песъчинки на земята. Ето пример, който дава идея за това какво е нужно да получите SHA-1 повторение. Ако всички 6.5 милиарда човека на земята програмираха, и всяка секунда всеки един от тях произвежда код еквивалентен на цялото Linux ядро (6.5 милиона Git обекта) и го изпраща в едно грамадно общо Git хранилище, биха били необходими около 2 години докато това хранилище получи толкова обекти, че да има 50% шанс от единично SHA-1 повторение. Така че, SHA-1 колизията е по-малко вероятна от това всеки член на екипа ви да бъде атакуван и убит от вълци в различно място в една и съща нощ. Ако заделите няколко хиляди долара за изчислителна мощ, възможно е да синтезирате два файла с един и същи хеш, както беше демонстрирано от https://shattered.io/ през февруари 2017г. Git постепенно преминава към SHA256 като хеширащ алгоритъм по подразбиране, който е много по-устойчив на collision атаки и има помощен код за смекчаване на този тип атаки (въпреки че, не може да ги елимиира изцяло). Референции към клонове Един прост начин да се обърнете към специфичен къмит, ако той е на върха в даден клон, е директно да използвате името на клона във всяка Git команда, която очаква референция към къмит. Например, ако искате да изследвате последния къмит в клон, следните две команди са еквивалентни, ако името на клона е topic1 и клонът сочи към къмита с хеш ca82a6d… : $ git show ca82a6dff817ec66f44342007202690a93763949 $ git show topic1 Ако искате да видите към кой специфичен SHA-1 сочи клона или да разберете как се представят тези примери по отношение на SHA-1 хешовете, можете да ползвате plumbing инструмент на Git наречен rev-parse . Можете да видите Git на ниско ниво за повече информация за plumbing инструментите; в общи линии, rev-parse се използва за операции на по-ниско ниво и не е предназначен за ежедневни дейности. Обаче, понякога той може да е полезен, ако искате да знаете какво се случва зад кулисите. Ето как можете да стартирате rev-parse във вашия клон. $ git rev-parse topic1 ca82a6dff817ec66f44342007202690a93763949 RefLog съкратени имена Едно от нещата, които Git прави на заден план докато вие работите, е да пази т. нар. “reflog” — дневник на това къде са били вашите HEAD и branch референции за последните няколко месеца. Можете да го видите с командата git reflog : $ git reflog 734713b HEAD@{0}: commit: Fix refs handling, add gc auto, update tests d921970 HEAD@{1}: merge phedders/rdocs: Merge made by the 'recursive' strategy. 1c002dd HEAD@{2}: commit: Add some blame and merge stuff 1c36188 HEAD@{3}: rebase -i (squash): updating HEAD 95df984 HEAD@{4}: commit: # This is a combination of two commits. 1c36188 HEAD@{5}: rebase -i (squash): updating HEAD 7e05da5 HEAD@{6}: rebase -i (pick): updating HEAD Всеки път, когато върхът на клона се обнови по каква да е причина, Git съхранява тази информация за вас в тази временна история. Можете да я използвате за да се обръщате към по-стари къмити. Например, ако искате да видите петата предишна стойност на HEAD на вашето хранилище, можете да използвате референцията @{5} , която се вижда в историята: $ git show HEAD@{5} Можете да ползвате същия синтаксис за да видите къде е бил клона преди определено време. Ако искате примерно да разбере в какво състояние е бил master клона вчера, можете да изпълните: $ git show master@{yesterday} Това ще ви покаже къде е сочил върха на master клона вчера. Тази техника обаче работи само за данни, които все още са в reflog историята, така че не можете да я използвате за къмити по-стари от няколко месеца. За да видите reflog информацията форматирана като git log изход, изпълнете git log -g : $ git log -g master commit 734713bc047d87bf7eac9674765ae793478c50d3 Reflog: master@{0} (Scott Chacon <schacon@gmail.com>) Reflog message: commit: Fix refs handling, add gc auto, update tests Author: Scott Chacon <schacon@gmail.com> Date: Fri Jan 2 18:32:33 2009 -0800 Fix refs handling, add gc auto, update tests commit d921970aadf03b3cf0e71becdaab3147ba71cdef Reflog: master@{1} (Scott Chacon <schacon@gmail.com>) Reflog message: merge phedders/rdocs: Merge made by recursive. Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' Важно е да се подчертае, че reflog информацията е строго локална — това е дневник на действията, които само вие сте извършили във вашето хранилище. Референциите няма да са същите в копието на хранилището на някой друг. Също така, веднага след като сте клонирали хранилище, ще имате празна reflog история, понеже се подразбира, че все още не са правени никакви промени по него. Ако изпълните git show HEAD@{2.months.ago} , ще видите съответния къмит само ако сте клонирали проекта поне два месеца преди това — ако сте го клонирали по-късно, ще видите само първия ви локален къмит. Подсказка Мислете за reflog историята като за Git версия на историята на вашия шел Ако имате опит с UNIX или Linux, можете да гледате на reflog дневника ви като за Git версия на вашата история на шела, която представлява списък на това, което само вие сте правили във вашата “сесия” и няма нищо общо с това, което друг потребител на операционната система би могъл да е вършил на същата машина. Забележка Escaping на скоби в PowerShell В PowerShell, скобите като { и } са специални символи и трябва да бъдат escaped. Можете да го направите с backtick ` или да поставите къмит обръщението в кавички: $ git show HEAD@{0} # will NOT work $ git show HEAD@`{0`} # OK $ git show "HEAD@{0}" # OK Йерархични референции Другият основен начин да укажете къмит е през неговото родословие. Ако поставите символа ^ в края на референция към къмит, Git ще намери неговия родител. Да допуснем, че историята на проекта ви изглежда така: $ git log --pretty=format:'%h %s' --graph * 734713b Fix refs handling, add gc auto, update tests * d921970 Merge commit 'phedders/rdocs' |\ | * 35cfb2b Some rdoc changes * | 1c002dd Add some blame and merge stuff |/ * 1c36188 Ignore *.gem * 9b29157 Add open3_detach to gemspec file list Сега, можете да видите предишния къмит указвайки HEAD^ , което означава “родителят на HEAD”: $ git show HEAD^ commit d921970aadf03b3cf0e71becdaab3147ba71cdef Merge: 1c002dd... 35cfb2b... Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' Забележка Префикс на символа в Windows В Windows и cmd.exe , ^ е специален символ и е необходимо да се третира по различен начин. Можете или да го напишете два пъти или да напишете къмит референцията в кавички: $ git show HEAD^ # няма да работи в Windows $ git show HEAD^^ # OK $ git show "HEAD^" # OK Можете да въведете и число след ^ за да укажете кой родител искате – например, d921970^2 означава “вторият родител на d921970.” Този синтаксис е полезен само за merge къмити, които имат повече от един родител — първият родител на merge къмит е от клона, в който сте били по време на сливането (често това е master ), докато вторият родител идва от клона, който е бил слят (примерно, topic ): $ git show d921970^ commit 1c002dd4b536e7479fe34593e72e6c6c1819e53b Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 14:58:32 2008 -0800 Add some blame and merge stuff $ git show d921970^2 commit 35cfb2b795a55793d7cc56a6cc2060b4bb732548 Author: Paul Hedderly <paul+git@mjr.org> Date: Wed Dec 10 22:22:03 2008 +0000 Some rdoc changes Символът ~ (тилда) също се използва за референция на унаследявания. Той също указва първия родител, така че HEAD~ и HEAD^ са еквивалентни. Разликата идва, когато укажете и число. HEAD~2 означава “първият родител на първия родител,” или “дядото” — това трасира първите родители толкова пъти, колкото е указано с числото. Например, в историята от преди малко, HEAD~3 ще бъде: $ git show HEAD~3 commit 1c3618887afb5fbcbea25b7c013f4e2114448b8d Author: Tom Preston-Werner <tom@mojombo.com> Date: Fri Nov 7 13:47:59 2008 -0500 Ignore *.gem Това може да се напише и като HEAD ~ , резултатът ще е същия: $ git show HEAD~~~ commit 1c3618887afb5fbcbea25b7c013f4e2114448b8d Author: Tom Preston-Werner <tom@mojombo.com> Date: Fri Nov 7 13:47:59 2008 -0500 Ignore *.gem Можете също да комбинирате тези символи — за да укажете втория родител на предишната референция (приемаме, че е бил merge къмит), използвайте HEAD~3^2 и т.н. Обхвати от къмити Видяхме как се указват единични къмити, нека да видим как може да реферираме и обхвати от къмити. Това е полезно при управлението на клонове — ако имате множество клонове код, можете да използвате подобен вид обръщения, за да отговорите на въпроси от рода на “Каква работа от този клон все още не съм слял в главния ми клон?” Две точки Най-обикновеният начин за указване на обхват е с две точки. Това указва на Git да намери множество къмити, които са достъпни от единия, но недостъпни от другия клон. Нека приемем, че имате история подобна на Примерна история за избор на обхват . Фигура 136. Примерна история за избор на обхват Да кажем, че искате да видите коя част от работата в клона experiment все още не е интегрирана в master клона. Можете да укажете на Git да покаже списък на само тези къмити с master..experiment — това означава “всички къмити достъпни през experiment , които не са достъпни през master .” За по-голяма яснота, в диаграмата къмитите са показани със символи: $ git log master..experiment D C Ако пък желаете да покажете обратното — всички къмити в master , които не са интегрирани в experiment — просто разменете имената на клоновете. experiment..master ви показва всичко от master , което е недостъпно през experiment : $ git log experiment..master F E Това е много полезно, ако държите да обновявате experiment с възможно най-новите данни и да видите какво предстои да сливате. Друго често използване на този синтаксис е когато искате да прегледате какво предстои да публикувате в отдалечено хранилище: $ git log origin/master..HEAD Тази команда ще отпечата всички къмити в текущия ви клон, които липсват в master клона на отдалеченото хранилище origin . Ако изпълните git push и текущият локален клон следи origin/master , то къмитите изведени от командата git log origin/master..HEAD ще са тези, които ще бъдат изпратени към сървъра. Можете също така да пропуснете името на клона от едната страна на двете точки и в такъв случай Git ще подразбира HEAD . Например, ще получите същия резултат като в предишния пример ако просто напишете git log origin/master.. — Git замества празното пространство в края с HEAD . Много точки Синтаксисът с две точки е удобен за съкращение, но може да искате да укажете повече от два клона за вашето търсене, така че да намерите кои са къмитите във всеки от произволен брой клонове, които не присъстват в текущия клон. Git позволява това със символа ^ или фразата --not изписани преди всяка референция от която не искате да виждате достъпни къмити. Така следните три команди са еднакви: $ git log refA..refB $ git log ^refA refB $ git log refB --not refA Това е хубаво, защото с този тип синтаксис можете да укажете повече от две референции в заявката, което не става при използване на две точки. Например, ако искате да видите всички къмити достъпни от клоновете refA или refB но не и през refC , можете да използвате една от следните команди: $ git log refA refB ^refC $ git log refA refB --not refC Това вече ви дава много мощна система за запитвания, която да ви помогне да видите какво съдържат клоновете ви. Три точки И последният основен начин за извличане на набор от къмити е т.нар. triple-dot синтаксис, който указва на Git да ви потърси всички къмити, които са достъпни от кой да е от двата клона, но не и от двата едновременно. Погледнете отново историята на къмитите от диаграмата Примерна история за избор на обхват . Ако искате да видите какво има в master или experiment но не и в двата клона, можете да изпълните: $ git log master...experiment F E D C Отново, това ви дава нормален log изход, но извежда информация само за тези 4 къмита в реда на датите им. Често използван параметър към тази команда е --left-right , който в допълнение ще ви покаже от коя страна на обхвата е всеки от намерените къмити. Това прави примера ни една идея по-полезен: $ git log --left-right master...experiment < F < E > D > C С тези инструменти можете по-лесно да накарате Git да ви покаже къмита или множеството от къмити, които искате да обследвате. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/sv/v2/Distribuerade-Git-Medverka-i-ett-projekt | Git - Medverka i ett projekt About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Distribuerade Git - Medverka i ett projekt Medverka i ett projekt Det svåra med att beskriva hur du gör för att bidra till ett projekt är att medverkan kan ske på mängder av olika sätt. Tack vare Gits flexibelt skiljer sig användningen åt, vilket gör det näst intill omöjligt att säga hur du borde göra — varje projekt arbetar på sitt sätt. Faktorer som påverkar hur ett projekt är organiserat är antalet aktivt involverade, överenskomna arbetsprocesser och fördelningen av behörigheter för att checka in kod Det finns dock några generella riktlinjer som kan hjälpa dig att komma igång. För det första — hur många involverade bidrar aktivt med källkod och hur ofta? I mindre pojekt är det vanligt att ett par, tre utvecklare gör några få incheckningar om dagen, kanske ännu färre om projektet är vilande. I större projekt, eller företag för den delen, kan hundratals utvecklare arbeta aktivt med kodbasen och bidra med tusentals incheckningar varje dag. Det är viktigt att känna till ungefär hur många som arbetar aktivt i kodbasen. Ju fler utvecklare, ju mer problem kan du stöta på för att få din kod att läggas till och integreras sömlöst. Under tiden du arbetar med dina ändringar, eller väntar på att få dem godkända, kan ny kod göra dem ofunktionella — eller rentav inaktuella. Hur kan du då göra för att din egen kodbas ska hållas uppdaterad och dina incheckningar aktuella? För det andra, hur ser projektets beslutade arbetsprocess ut? Är det en centraliserad process, så att varje utvecklare har samma skrivrättigheter till koden på huvudgrenen? Har projektet en förvaltare eller integrationsansvarig som granskar alla patcher? Ska samtliga patcher granskas och godkännas av en annan utvecklare? Kommer du att vara involverad i den processen? Eller finns det ett kvalitetsledningssystem med testare på plats som du behöver skicka dina ändringar till först? Till sist spelar behörigheter för incheckningar in. Din medverkan kommer att skilja sig mycket åt beroende på om du har skrivrättigheter till kodbasen eller inte. Om du inte har det, hur ser processen ut för att granska och godkänna bidrag? Finns det ens en sådan process? Hur många ändringar ska skickas med i taget? Hur ofta? Alla dessa frågor påverkar hur du bäst bidrar till ett projekt, liksom vilka arbetssätt du själv föredrar eller har tillgång till. Vi kommer att gå igenom tillvägagångssätten ur olika aspekter i en serie användarfall, från enkla till mer komplexa. Du borde känna igen det specifika arbetssätt du förväntas använda i dessa exempel. Riktlinjer för incheckningar Innan vi går in på användarfallen kommer en kort kommentar om incheckningsmeddelanden. Att ha bra riktlinjer för incheckningar, och att hålla sig till dem, gör det betydligt enklare att använda Git tillsammans med andra. I Git-projektet finns ett dokument med flera bra tips på saker att tänka på för att göra incheckningar till en patch. Du hittar det i filen Documentation/SubmittingPatches i Gits källkod. Först av allt, så bör dina bidrag inte ha några felaktiga mellanslag. Git har ett lätt sätt att kontrollera det — innan du gör en incheckning, kör kommandot git diff --check . Det ger dig en lista över möjliga mellanslag som kan vara felaktiga. Figur 57. Output of git diff --check . Kör kommandot innan en incheckning för att snabbt kontrollera om du är på väg att checka in mellanslag som kan irritera andra utvecklare. För det andra, försök att göra varje incheckning till logiskt separat enhet. Om du kan, försök att hålla dina ändringar lättsmälta - koda inte en hel helg på fem olika uppgifter, för att sen skicka dem som en enda gigantisk incheckning på måndan. Även om du inte har checkat in på en hel helg, använd köområdet för att dela upp ditt arbete i minst fem incheckningar på måndagen, med ett tydligt meddelande per incheckning. Om några av ändringarna är i samma fil, försök att använda git add --patch för att delvis köa filer (läs mer i Interactive Staging ). Projektets ögonblicksbild längst ut på grenen kommer att se likadan ut oavsett om du gör en incheckning eller fem, så länge som alla ändringar läggs till förr eller senare. Försök därför att göra det så enkelt som möjligt för dina kollegor när de ska granska dina ändringar. Med det tillvägagångssättet blir det också enklare att dra ut eller återställa någon av ändringarna i efterhand, om det skulle behövas. I avsnittet Rewriting History finns en mängd användbara tips för att skriva om Git-historiken och interaktivt köa filer — använd dessa verktyg för att få en logisk och förståelig historik innan du skickar arbetet vidare till någon annan. Slutligen behövs en struktur för incheckningsmeddelandet. Med vanan att alltid skriva bra meddelanden blir användningen av - och samarbetet i - Git betydligt enklare. Tumregeln är att dina meddelanden ska börja med en mening på max 50 tecken som sammanfattar ändringen, följt av en blank rad och en mer detaljerad beskrivning. Git-projektet gör gällande att beskrivningen bör inkludera anledningen till ändringen och en jämförelse med tidigare beteende — det är en bra riktlinje att följa. Det är också bra att skriva i imperativ form. Med andra ord, ge order. Istället för “Jag lade till test för” eller “Lägger till test för,” skriv “Lägg till test för” Här är en mall ursprungligen skriven av Tim Pope : Kort (50 tecken max), befallande sammanfattning Mer detaljerad text, om nödvändigt. Håll den till cirka 72 tecken eller så. Första raden kan ofta jämföras med ämnet på ett mejl och resten av innehållet med brödtexten. Den tomma raden mellan titel och brödtext är absolut nödvändig (om du inte utelämnar innehållet helt); verktyg som ombasera kan bli förvirrade om de skrivs ihop. Ytterligare paragrafer skrivs efter en tom rad. - Punktlistor är också ok - Efter en tom rad och ett inledande mellanslag används ofta bindestreck eller asterisk som punkt, men det finns olika konventioner. Om alla dina incheckningsmeddelande följer den här mallen kommer det att bli lättare, både för dig och dem du samarbetar med. Git-projektet har välformatterade incheckningsmeddelanden — kör git log --no-merges där för att få inspiration till hur en väl formatterad incheckningshistorik kan se ut. Notera Gör som vi säger och inte som vi gör För att vara helt ärliga, många av exemplen i den här boken har inte så värst välformatterade incheckningsmeddelanden; vi använder ofta -m efter git commit , helt enkelt. Som sagt, gör som vi säger, inte som vi gör. Privat, litet team Det enklaste arbetssättet du sannolikt kommer stöta på är ett privat projekt med en eller två involverade utvecklare. I den här kontexten betyder “privat” sluten källkod — den är inte tillgänglig för någon utomstående. Du och de andra utvecklarna har skrivbehörigheter till arkivet. I den här uppsättningen liknar arbetssättet det som du kanske stöter på när du använder Subversion eller något annat centraliserat versionshanteringssystem. Du behåller fördelarna med saker som att kunna checka in offline, en betydligt enklare förgrening och sammanslagning, men arbetsprocesserna är mycket lika; den största skillnaden är att sammanslagningar sker i klienten istället för från servern vid incheckning. Låt oss ta ett exempel på hur det kan gå till när två utvecklare börjar samarbeta i ett gemensamt arkiv. Den första utvecklaren, John, klonar arkivet och gör en ändring som checkas in lokalt. (Informationsmeddelandena har ersatts med ... för att korta ner exemplen.) # Johns dator $ git clone john@githost:simplegit.git Klonar till 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'remove invalid default value' [master 738ee87] remove invalid default value 1 fil ändrad, 1 tillagd(+), 1 borttagen(-) Jessika, den andra utvecklaren, gör samma sak — klonar arkivet och checkar in en ändring: # Jessikas dator $ git clone jessika@githost:simplegit.git Klonar till 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 fil ändrad, 1 tillagd(+), 0 borttagen(-) Sen skickar Jessika sina ändringar till servern, vilket funkar bra: # Jessikas dator $ git push origin master ... Till jessika@githost:simplegit.git 1edee6b..fbff5bc master -> master Den sista raden i outputen är ett användbart meddelande från sändningen. Formateringen är <gammalref>..<nyref> frånref -> tillref , där gammalref betyder tidigare referens, nyref är den nya referensen, frånref är namnet på den lokala referens som ändringen kommer från och tillref är fjärreferensen som har blivit uppdaterad. Du kommer att se liknande output i exemplen nedanför, en grundförståelse kommer göra det lättare att förstå innebörden av arkivens varierade stadier. Mer detaljer finns i git-push dokumentation. För att fortsätta med det här exemeplet — kort efteråt gör John några ändringar, checkar in dem lokalt och försöker skicka dem till samma server som Jessika: # Johns dator $ git push origin master Till john@githost:simplegit.git ! [refuserad] master -> master (ej snabbspolad) error: misslyckades sända vissa referenser till 'john@githost:simplegit.git' I det här fallet kan John inte skicka sina incheckningar på grund av Jessikas tidigare incheckning av sina ändringar. Det här är särskilt viktigt att förstå om du tidigare har använt Subversion, för du kommer att märka att de två utvecklarna inte ändrade i samma fil. Subversion gör en sammanslagning automatiskt på servern om olika filer har ändrats, men med Git behöver du själv först sammanfoga incheckningarna lokalt. Med andra ord, John måste först hämta Jessikas ändringar i fjärrarkivet och sammanfoga dem i sitt lokala arkiv innan han kommer att få tillåtelse att skicka ändringarna. Som ett första steg hämtar John Jessikas ändringar(Jessikas ändringar hämtas bara, de slås inte ihop med hans filer): $ git fetch origin ... Från john@githost:simplegit + 049d078...fbff5bc master -> origin/master Johns arkiv ser nu ut ungefär så här: Figur 58. Johns divergerande historik. Nu kan John slå ihop de ändringar han hämtade av Jessika med filerna på sin dator: $ git merge origin/master Sammanslagning gjord med metoden 'recursive'. TODO | 1 + 1 fil ändrad, 1 tillägg(+), 0 borttagna(-) Om den lokala sammanslagningen går smidigt kommer Johns uppdaterade historik se ut ungefär så här: Figur 59. Johns arkiv efter sammanslagning av ändringar från origin/master . Nu kanske John vill testa den nya koden för att vara helt säker på att ingen av Jessikas ändringar påverkat hans, och om allt går bra kan han slutligen skicka sina sammanslagna ändringar till servern: $ git push origin master ... Till john@githost:simplegit.git fbff5bc..72bbc59 master -> master Till sist ser Johns incheckningshistorik ut så här: Figur 60. Johns historik eftervatt ha skickat sina ändringar till servern origin . Under tiden har Jessika skapat en ny gren med namnet issue54 , och gjort tre incheckningar till den nya grenen. Hon har inte hämtat Johns ändringar än, så hennes incheckningshistorik ser ut så här: Figur 61. Jessikas gren. Plötsligt får Jessika veta att John har skickat nya ändringar till servern och vill kika på dem, så hon hämtar alla ändringar från servern med kommandot: # Jessikas dator $ git fetch origin ... Från jessika@githost:simplegit fbff5bc..72bbc59 master -> origin/master Nu hämtas Johns incheckade ändringar ner. Jessikas historik kommer att se ut så här: Figur 62. Jessikas historik efter att ha hämtat Johns ändringar. Jessika tycker att ändringarna på hennes nya gren är klara, men hon vill veta vilka delar av Johns arbete som hon måste slå ihop med sitt arbete så att hon kan skicka dem. Hon kör git log för att få reda på det: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Författare: John Smith <jsmith@example.com> Datum: Fri May 29 16:01:27 2009 -0700 ta bort ogiltigt standardvärde Syntaxen issue54..origin/master används för att filtrera loggar. Git ombeds att bara visa de incheckningar i den senare referensen ( origin/master i det här fallet) som inte finns på den första referensen (här issue54 ). Vi kommer att gå igenom syntaxen i detalj i avsnitt Commit Ranges . Från ovanstående output kan vi utläsa att det bara är en enda av Johns incheckningar som Jessika inte har slagit ihop med sitt arbete lokalt. Om hon slår ihop sina ändringar med ändringarna på origin/master är det bara den incheckningen som kommer att påverka hennes lokala arkiv. Nu kan Jessika slå ihop sin lokala funktionsgren med sin huvudgren, slå samman Johns ändringar ( origin/master ) med sin master gren och sen skicka sitt arbete till servern igen. . När alla ändringar på grenen issue54 har checkats in, börjar Jessika med att byta tillbaka till sin huvudgren: $ git checkout master Byter till gren 'master' Din gren ligger efter 'origin/master' med 2 incheckningar, kan snabbspolas. Jessika kan slå ihop antingen origin/master eller issue54 först — de är båda uppströms, så ordningen spelar ingen roll. Den slutliga ögonblicksbilden blir identisk oavsett vilken ordning hon väljer, det är bara historiken som kommer att skilja sig åt. Hon bestämmer sig för att slå ihop grenen issue54 först: $ git merge issue54 Uppdaterar fbff5bc..4af4298 Snabbspolar README | 1 + lib/simplegit.rb | 6 +++++- 2 filer ändrade, 6 tillägg(+), 1 borttagen(-) Inget oväntat händer, som du kan se var det en sammanslagning som kunde snabbspolas framåt. Jessika kan nu avsluta sammanslagningarna lokalt genom att slå ihop de ändringar hon hämtade tidigare från John och som är väntar kvar på origin/master : $ git merge origin/master Slår ihop lib/simplegit.rb automatiskt Sammanslagning gjorde med metoden 'recursive'. lib/simplegit.rb | 2 +- 1 fil ändrad, 1 tillägg(+), 1 borttagning(-) Allt slogs ihop smidigt, Jessikas historik ser nu ut så här: Figur 63. Jessikas historik efter att ha slagit ihop Johns ändringar. Fjärreferensen origin/master kan nås från Jessikas huvudgren, så hon borde kunna skicka sina ändringar utan problem (förutsatt att John inte har skickat fler ändringar under tiden): $ git push origin master ... Till jessika@githost:simplegit.git 72bbc59..8059c15 master -> master Båda utvecklarna har nu checkat in sina versioner av filerna några gånger och fått in varandras ändringar i sina lokala kodbaser. Figur 64. Jessikas historik efter att ha skickat tillbaka ändringarna till servern. Det här är en av de enklaste arbetsprocesserna. Du arbetar ett tag (vanligtvis i en funktionsgren), och slår ihop arbetet i huvudgrenen när det är klart. När du vill dela ditt arbete, hämtar du och slår ihop din huvudgren med origin/master och skickar tillbaka din huvudgren till servern. Den generella arbetsprocessen ser ut ungefär så här: Figur 65. Generell arbetsprocess med Git för flera utvecklare. Privat större team Nästa exempel är medverkan i ett större, privat team. Här tittar vi närmre på hur arbetsprocessen kan se ut när mindre team samarbetar på features, som därefter slås ihop av andra team. Säg att John och Jessika arbetar tillsammans på en funktion (vi kallar den “featureA”). Samtidigt samarbetar Jessika och en tredje utecklare, Josie, på en annan, (“featureB”). I det här fallet använder sig företaget av en slags integrationsstyrt arbetsprocess, där arbetet av ett enskilt team slås samman med huvudgrenen av specifika ingengörer. Arkivets huvudgren kan endast uppdateras av dessa. Allt arbete sker på förgreningar som sedan slås ihop av andra i ett senare skede. Vi följer med Jessika medan hon arbetar på sina features parallellt, med två olika utvecklare, i en sådan här miljö. Vi utgår ifrån att hon redan har klonat arkivet, när hon bestämmer sig för att börja med featureA . Hon skapar en ny gren för funktionen och jobbar lite på den: # Jessikas dator $ git checkout -b featureA Bytte till en ny gren 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 fil ändrades, 1 tillägg(+), 1 borttagning(-) I det här läget behöver hon dela sitt jobb med John, så hon skickar sin featureA -gren med incheckningarna till servern. Jessika har inte behörighet att slå ihop sina ändringar med huvuudgrenen, så hon behöver skicka dem till en annan gren för att kunna samarbeta med John: $ git push -u origin featureA ... Till jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessika mejlar John för att berätta att hon har skickat ändringar till en gren med namnet featureA och att han kan kolla på dem nu. Medan hon väntar på feedback från John bestämmer hon sig för att börja jobba på featureB tillsammans med Josie. Hon börjar med att skapa en ny gren från serverns huvudgren: # Jessikas dator $ git fetch origin $ git checkout -b featureB origin/master Bytte till en ny gren 'featureB' Nu gör Jessika ett par inckeckningar på `featureB`grenen: `[source,console] $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 fil ändrad, 1 tillägg(+), 1 borttagen(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 fil ändrad, 5 tillägg(+), 0 borttagna(-) Jessikas arkiv ser nu ut så här: Figur 66. Jessikas initiala versionshistorik. Hon är redo att skicka sina ändringar när hon får ett mejl från Josie som skriver att en gren hon har börjat på för featureB redan har skickats till servern som grenen featureBee . Jessika behöver slå ihop de ändringarna med sina innan hon kan skicka sitt arbete till den gren Josie skickat till servern. Jessika hämtar först Josies ändringar med git fetch : $ git fetch origin ... Från jessika@githost:simplegit * [new branch] featureBee -> origin/featureBee Om vi antar att Jessika fortfarande är utcheckad på grenen featureB , så kan hon nu slå Josies arbete med den grenen med kommandot git merge : $ git merge origin/featureBee Slår ihop lib/simplegit.rb automatiskt. Sammanslagning gjord med metoden 'recursive'. lib/simplegit.rb | 6 ++++++ 1 fil ändrad, 6 tillägg(+), 0 borttagna(-) Sammanslagning gjord med metoden 'recursive'. lib/simplegit.rb | 4 ++++ 1 fil ändrad, 4 tillägg(+), 0 borttagna(-) I det här läget vill Jessika skicka allt som finns på featureB tillbaka till servern, men utan att skicka upp sin egna gren. Eftersom Josie redan har påbörjat en uppströms featureBee -gren så vill Jessika skicka till den grenen. Det gör hon med: $ git push -u origin featureB:featureBee ... Till jessick@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee Detta kallas för en referensspecifikation . Se The Refspec för mer information om Gits referensspecifikationer och hur du kan använda dem. Lägg också märke till -u -flaggan; det är en kortversion av kommandot --set-upstream , som sparar en referens till den fjärrgren som din lokala gren spårar. Plötsligt får Jessika ett mail från John, som berättar att han har skickat några ändringar till featureA -grenen och ber henne kolla på dem. Återigen kör Jessika ett enkelt git fetch för att hämta allt nytt innehåll från servern, inklusive Johns senaste arbete: $ git fetch origin ... Från jessika@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessika kan nu läsa loggarna med Johns senaste ändringar genom att jämföra innehållet som hämtades för featureA med den lokala kopian av samma gren: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Författare: John Smith <jsmith@example.com> Datum: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 Om Jessika gillar det hon ser kan hon fusionera Johns nya arbete till sin lokala featureA gren med: $ git checkout featureA Bytte till gren 'featureA' $ git merge origin/featureA Uppdaterar 3300904..aad881d Snabbspolar lib/simplegit.rb | 10 +++++++++- 1 fil ändrad, 9 tillägg(+), 1 borttagen(-) Till sist kanske Jessika vill göra några mindre ändringar i det sammanslagna innehållet. Hon har full frihet att göra sina ändringar, checka in dem till sin lokala gren featureA och skicka tillbaka slutresultatet till servern. $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 fil ändrad, 1 tillägg(+), 1 borttagen(-) $ git push ... Till jessika@githost:simplegit.git 3300904..774b3ed featureA -> featureA Jessikas incheckningshistorik kommer nu att se ut ungefär så här: Figur 67. Jessikas historik efter incheckningar till funktionsgrenen. Vid någon tidpunkt kommer Jessika, John och Josie att behöva informera dem som ansvarar för huvudgrenen att featureA och featureB är redo att slås ihop med den. När sammanslagningen med huvudgrenen då är klar, kommer en hämtning av den att få med den nya versionsincheckningen. Historiken kommer då att se ut så här: Figur 68. Jessikas historik efter sammanslagning av ämnesgrenar med huvudgren. Många byter till Git på grund av möjligheten för flera team att arbeta parallellt och kombinera sina förgreningar sent i processen. Möjligheten att mindre grupperingar inom ett team kan samarbeta via fjärrgrenar utan att nödvändigtvis behöva involvera hela teamet är utan tvekan en av Gits stora fördelar. Arbetsprocessen som precis har beskrivts ser ut ungefär såhär: Figur 69. Grundläggande arbetsprocess för flera team. Öppet, litet projekt Att bidra till öppna projekt är ofta lite annorlunda än privata. Eftersom du vanligtvis inte har behörighet att göra ändringar direkt i projektet behöver förvaltarna få ditt arbete på något annat sätt. I det första exemplet ska vi titta på hur man förgrenar ett arkiv på de hostingsajter för Git som tillåter det. Många hostingsajter har stöd för förgreningar, (såsom GitHub, BitBucket, repo.or.cz med flera) och många projektansvariga förväntar sig att andra medverkar på det sättet. Det andra exemplet beskriver arbetsprocessen i de projekt som istället föredrar att acceptera patchade bidrag via mejl. Det första du behöver göra är troligen att klona grundarkivet och skapa en funktionsgren för patcherna du planerar att bidra med Flödet ser helt enkelt ut så här: $ git clone <url> $ cd project $ git checkout -b featureA ... arbeta ... $ git commit ... arbeta ... $ git commit Notera Du kanske kommer att vilja använda rebase -i för att komprimera ditt arbete till en enda incheckning, eller arrangera om incheckningnarna så att de blir enklare för de ansvariga att granska — se Rewriting History för mer information om att ombasera grenar interaktivt. När arbetet är klart och du är redo att dela det med förvaltarnas, gå till ursprungsarkivets projektsida och klicka på knappen ``Fork`` för att skapa en kopia av projektet som du har full behörighet till. Därefter lägger du till det nya repots URL som ett nytt fjärrarkiv för ditt lokala arkiv; i det här exemplet kan vi kalla det för mingaffel : $ git remote add mingaffel <url> Sedan behöver du skicka ditt arbete till det här arkivet. Det är enklare att skicka den finessgren du arbetar på till ditt kopierade arkiv än att fusionera det arbetet i din huvudgren och fusionera den. Om ditt arbete inte bli godkänt, eller om din incheckning inte blir cherry-pickad, så slipper du spola tillbaka din huvudgren (läs mer om Gits cherry-pick i Arbetsflöden med ombasering och plocka russin ur kakan ). Om de ansvariga å andra sidan slår ihop, ombaserar eller cherry-pickar din funktion, så kommer du att få tillbaka den genom att dra ner ändringar från deras repo ändå. Hur du än gör kan du skicka ditt arbete med: $ git push -u mingaffel featureA När ditt arbete har skickats till din förgrening av arkivet behöver du meddela förvaltarna av originalprojektet att du har arbete som du skulle vilja att de slår samman. Detta kallas ofta för en pull request och du behöver vanligtvis göra en sådan begäran antingen via websida — GitHub har sin egen ``Pull Request``-mekanism som vi kommer att gå igenom i GitHub — eller så kan du köra kommandot git request-pull och mejla den efterföljande utdatan till de ansvariga. Kommandot git request-pull tar basgrenenen, det vill säga den gren du vill att din funktionsgren dras in i, och Git-arkivets URL som du vill att de accepterar kod ifrån, och sammanfattar alla ändringar du begär ska tas in. Om Jessika till exempel vill skicka en pull request till John, och hon har gjort två incheckningar på funktionsgrenen som hon just har skickat, så kan hon använda det så här: $ git request-pull origin/master mingaffel Följande ändringar sen incheckning 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessika Smith (1): added a new function är tillgängliga i git-arkivet på: git://githost/simplegit.git featureA Jessika Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 fil ändrad, 9 tillägg(+), 1 borttagning(-) Den här utdatan kan skickas till de ansvariga — den beskriver från vilken gren arbetet förgrenades, ger en sammanfattning av incheckningarna och varifrån den nya funktionen kan hämtas. I ett projekt där du inte är ansvarig är det oftast enklast att ha en huvudgren, t.ex master , som alltid följer origin/master och sen arbeta i funktionsgrenar som du enkelt kan radera om de inte godkänns. Att isolera funktioner tll funktionsgrenar gör det också lättare för dig att flytta ditt arbete om änden på huvudarkivet har rört sig under tiden du arbetat så att din version inte längre kan sammanfogas på ett smidigt sätt. Om du till exempel vill skicka in en andra funktionsgren till projektet, fortsätt inte att arbeta på den funktionsgren du nyss skickade upp — börja istället om från arkivets huvudgren: $ git checkout -b featureB origin/master ... arbeta ... $ git commit $ git push mingaffel featureB $ git request-pull origin/master myfork ... e-postbrevet genererar förfrågan att hämta till ansvarig ... $ git fetch origin Now, each of your topics is contained within a silo — similar to a patch queue — that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so: Nu är båda dina funktioner i varsitt silo — som en kö för patchar — som du kan skriva om, ombasera och ändra utan att funktionerna påverkar eller blir beroende av varandra: Figur 70. Initial versionshistorik för featureB . Om vi säger att projektets ansvariga har dragit in ett gäng andra patches innan de testar din första gren, så kan den inte sammanfogas automatiskt. I det här fallet kan du försöka att ombasera den grenen så att den hamnar längst ut på toppen av origin/master , lösa eventuella konflikter och skicka in din version igen: $ git checkout featureA $ git rebase origin/master $ git push -f mingaffel featureA Det här skriver om historiken enligt bilden nedan Versionshistorik efter avslutat arbete med featureA . . Figur 71. Versionshistorik efter avslutat arbete med featureA . Eftersom du flyttade grenen behöver du ange -f till ditt kommando för att kunna ersätta serverns featureA -gren med en annan incheckning än den ursprungliga. Ett alternativ vore att skicka det här nya arbetet till en annnan gren på servern (som kanske kan heta featureAv2 ), Vi tittar närmre på ytterligare ett alternativ: ansvariga har tittat ändringarna i din andra gren och gillar dem mestadels, men de skulle vilja att du gjorde en justering. Du använder möjligheten att flytta förgreningen från featureA till huvudgrenen. Du kan göra det här genom att skapa en ny gren från origin/master , sammanfoga featureB där, lösa eventuella konflikter, göra ändringen och skicka det som en ny gren: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... justera ... $ git commit $ git push mingaffel featureBv2 Flaggan --squash komprimerar alla incheckningar på grenen som ska slås ihop till en enda versionsändring, vilket ger samma status i arkivet som vid en sammanslagning. Det innnebär att dina framtida incheckningar bara kommer att ha en förälder och ger dig möjlighet att dra in alla ändringar från en annan gren och göra fler ändringar innan den nya incheckningen kommer på pränt. Ibland kan det vara användarbart att använda flaggan --no-commit för att fördröja en ny incheckning vid en sammanslagning istället för som i den ordinarie sammanslagningsprocessen. I det här läget kan du meddela ansvarig att du har gjort de begärda ändringarna och att de kan hitta dessa i din featureBv2 . Figur 72. Versionshistorik efter featureBv2 . Öppet, större projekt via mejl Många projekt har sina rutiner för att acceptera patchar — du behöver kolla upp de specifika reglerna för varje projekt, eftersom de kommer att skilja sig åt. Eftersom det finns flera äldre, större projekt som endast accepterar patchar via en mejllista för utvecklare, så kommer vi att gå igenom ett exempel på hur det går till. Arbetsprocessen liknar den i föregående exemplet — du skapar finessgrenar som du arbetar på. Den stora skillnaden är att du inte kan skicka dina inceckningar till fjärrarkivet. Istället behöver du mejla varje commit till en mejllista för utvecklare. $ git checkout -b topicA ... arbeta ... $ git commit ... arbeta ... $ git commit Nu har du två incheckningar som du vill skicka till mejllistan. För att generera mbox-formatterade filer som du kan mejla till listan, använder du git format-patch — det gör om varje incheckning till ett mejl med den första raden i incheckningsmeddelandet som ämne och resten av meddelandet plus patchen som innehåll. Det fina med det här är att när en patch från ett mejl genererat med format-patch appliceras, så bevaras incheckningsinformationen korrekt. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch format-patch -kommandot skriver ut namnen på de patchfiler som skapas. Flaggan -M talar om för Git att leta efter omdöpta filer. Filerna kommer att se ut så här: $ cat 0001-add-limit-to-log-function.patch Av 330090432754092d704da8e76ca5c05c198e71a8 Mån Sep 17 00:00:00 2001 Från: Jessica Smith <jessica@example.com> Datum: Sön, 6 apr 2008 10:17:23 -0700 Ämne: [PATCH 1/2] add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 fil ändrad, 1 tillagd(+), 1 borttagen(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 Du kan också redigera patchfilerna för att lägga till mer information till mejllistan som du inte vill ska visas i incheckningsmeddelandet. Om du lägger till text mellan raden --- och början av patchen (inleds med raden diff --git ), så kan utvecklarna läsa meddelandet, men det ignoreras i patchningsprocessen. Det är en bra plats att lägga till information om varför du gjorde ändringarna, eller om du har några speciella instruktioner för att testa dem. För att skicka patchfilen till mejllistan kan du antingen klistra in innehållet i ditt mejlprogram eller skicka det via kommandoraden. Att klistra in texten orsakar ofta formatteringsproblem, speciellt med “smartare” klienter som inte bevarar radbrytningar och mellanslag korrekt. Som tur är har Git ett verktyg som hjälper dig att skicka korrekt formatterade patchar via IMAP, vilket gör det enklare. Vi kommer att visa hur du skickar en patch via Gmail, som råkar vara den e-postklient vi känner till bäst. Du kan läsa detaljerade instruktioner för en mängd e-postklienter i slutet av filen Documentation/SubmittingPatches i Gits källkod. Först behöver du sätta upp IMAP-sektionen i din ~/.gitconfig -fil. Du kan sätta varje värde separat med en serie git config -kommandon, eller lägga till dem manuellt. I slutänden ska din konfigurationsfil se ut något så här: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false Om din IMAP-server inte använder SSL så är de två sista raderna nog inte nödvändiga, och värdet för host kommer då att vara imap:// istället för imaps:// . När det är inställt kan du använda git imap-send för att placera patchserien i mappen Drafts på den angivna IMAP-servern: $ cat *.patch |git imap-send Analyserar imap.gmail.com... ok Ansluter till [74.125.142.109]:993... ok Loggar in... skickar 2 meddelanden 100% (2/2) klart Nu borde du kunna gå till din Drafts-mapp, ändra To-fältet till mejllistan du ska skicka patchen till, eventuellt lägga till cc:a till den person som är ansvarig, och skicka iväg det. Du kan också skicka patcharna via en SMTP-server. Precis som tidigare kan du sätta varje värde separat med en serie git config -kommandon, eller lägga till dem manuellt i ~/.gitconfig -filen: [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 När det är inställt kan du använda git send-email för att skicka patcharna: $ git send-email *.patch 0001-added-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Från vem ska breven skickas? [Jessica Smith <jessica@example.com>] E-postbreven kommer att skickas från: Jessica Smith <jessica@example.com> Till vem ska breven sändas (om någon)? jessica@example.com Message-ID att använda som In-Reply-To för det första brevet? y Git kommer att ställa en rad frågor om hur du vill att e-posten ska se ut för varje skickad patch. De kommer att se ut ungefär så här: (mbox) Lägger till cc: Jessica Smith <jessica@example.com> från \line 'From: Jessica Smith <jessica@example.com>' OK. Loggen säger: Sendmail: /usr/sbin/sendmail -i jessica@example.com Från: Jessica Smith <jessica@example.com> Till: jessica@example.com Ämne: [PATCH 1/2] added limit to log function Datum: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Sammanfattning I den här delen har vi gått igenom en mängd olika arbetsflöden för olika slags Git-projekt som du troligen kommer att stöta på, samt introducerat ett par nya verktyg för att hjälpa dig att hantera processerna. I nästa del kommer du att få lära dig hur du hanterar den andra sidan av myntet: att underhålla ett Git-projekt. Du får lära dig att vara en välvillig diktator eller integrationsansvarig. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Deshacer-Cosas | Git - Deshacer Cosas About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.4 Fundamentos de Git - Deshacer Cosas Deshacer Cosas En cualquier momento puede que quieras deshacer algo. Aquí repasaremos algunas herramientas básicas usadas para deshacer cambios que hayas hecho. Ten cuidado, a veces no es posible recuperar algo luego que lo has deshecho. Esta es una de las pocas áreas en las que Git puede perder parte de tu trabajo si cometes un error. Uno de las acciones más comunes a deshacer es cuando confirmas un cambio antes de tiempo y olvidas agregar algún archivo, o te equivocas en el mensaje de confirmación. Si quieres rehacer la confirmación, puedes reconfirmar con la opción --amend : $ git commit --amend Este comando utiliza tu área de preparación para la confirmación. Si no has hecho cambios desde tu última confirmación (por ejemplo, ejecutas este comando justo después de tu confirmación anterior), entonces la instantánea lucirá exactamente igual y lo único que cambiarás será el mensaje de confirmación. Se lanzará el mismo editor de confirmación, pero verás que ya incluye el mensaje de tu confirmación anterior. Puedes editar el mensaje como siempre y se sobreescribirá tu confirmación anterior. Por ejemplo, si confirmas y luego te das cuenta que olvidaste preparar los cambios de un archivo que querías incluir en esta confirmación, puedes hacer lo siguiente: $ git commit -m 'initial commit' $ git add forgotten_file $ git commit --amend Al final terminarás con una sola confirmación - la segunda confirmación reemplaza el resultado de la primera. Deshacer un Archivo Preparado Las siguientes dos secciones demuestran cómo lidiar con los cambios de tu área de preparación y tú directorio de trabajo. Afortunadamente, el comando que usas para determinar el estado de esas dos áreas también te recuerda cómo deshacer los cambios en ellas. Por ejemplo, supongamos que has cambiado dos archivos y que quieres confirmarlos como dos cambios separados, pero accidentalmente has escrito git add * y has preparado ambos. ¿Cómo puedes sacar del área de preparación uno de ellos? El comando git status te recuerda cómo: $ git add . $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md Justo debajo del texto “Changes to be committed” (“Cambios a ser confirmados”, en inglés), verás que dice que uses git reset HEAD <file>... para deshacer la preparación. Por lo tanto, usemos el consejo para deshacer la preparación del archivo CONTRIBUTING.md : $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md El comando es un poco raro, pero funciona. El archivo CONTRIBUTING.md esta modificado y, nuevamente, no preparado. Nota git reset puede ser un comando peligroso, especialmente si lo llamas con la opción --hard . Sin embargo, en el escenario descrito anteriormente, el archivo que está en tu directorio de trabajo no se toca, por lo que es relativamente seguro. Por ahora lo único que necesitas saber sobre el comando git reset es esta invocación mágica. Entraremos en mucho más detalle sobre qué hace reset y cómo dominarlo para que haga cosas realmente interesantes en Reiniciar Desmitificado . Deshacer un Archivo Modificado ¿Qué tal si te das cuenta que no quieres mantener los cambios del archivo CONTRIBUTING.md ? ¿Cómo puedes restaurarlo fácilmente - volver al estado en el que estaba en la última confirmación (o cuando estaba recién clonado, o como sea que haya llegado a tu directorio de trabajo)? Afortunadamente, git status también te dice cómo hacerlo. En la salida anterior, el área no preparada lucía así: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Allí se te indica explícitamente como descartar los cambios que has hecho. Hagamos lo que nos dice: $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Ahora puedes ver que los cambios se han revertido. Importante Es importante entender que git checkout -- [archivo] es un comando peligroso. Cualquier cambio que le hayas hecho a ese archivo desaparecerá - acabas de sobreescribirlo con otro archivo. Nunca utilices este comando a menos que estés absolutamente seguro de que ya no quieres el archivo. Para mantener los cambios que has hecho y a la vez deshacerte del archivo temporalmente, hablaremos sobre cómo esconder archivos ( stashing , en inglés) y sobre ramas en [ch03-git-branching] ; normalmente, estas son las mejores maneras de hacerlo. Recuerda, todo lo que esté confirmado en Git puede recuperarse. Incluso commits que estuvieron en ramas que han sido eliminadas o commits que fueron sobreescritos con --amend pueden recuperarse (véase Recuperación de datos para recuperación de datos). Sin embargo, es posible que no vuelvas a ver jamás cualquier cosa que pierdas y que nunca haya sido confirmada. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/pl/legal/impressum | Impressum | Atlassian Close Czy wyświetlić tę stronę w Twoim języku ? Wszystkie języki Wybierz swój język 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Zacznij korzystać za darmo Produkty Polecane Programiści Menedżerowie produktu Specjaliści IT Zespoły biznesowe Kadra zarządzająca Polecane Programiści Menedżerowie produktu Specjaliści IT Zespoły biznesowe Kadra zarządzająca Wyświetl wszystkie aplikacje Polecane Polecane aplikacje Jira Elastyczne zarządzanie projektami Confluence Wspólna przestrzeń robocza wiedzy Jira Service Management Dostarczanie usług z dużą prędkością ATLASSIAN COLLECTIONS Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Pewna optymalizacja strategii i wyników Focus • Talent • Align Szybkie świadczenie usług Jira Service Management • Customer Service Management • Zasoby • Rovo Szybkie dostarczanie oprogramowania wysokiej jakości Rovo Dev • DX • Pipelines • Bitbucket • Compass Obsługiwane przez Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Programiści Jira Elastyczne zarządzanie projektami Compass Katalog oprogramowania dla zespołów Procesy organizacji produkcji Skalowalna automatyzacja CI/CD Bitbucket Kod źródłowy i CI/CD DX (W oczekiwaniu na przejęcie) Mierz wydajność oraz wpływ sztucznej inteligencji Rovo Dev Oparte na sztucznej inteligencji agenty dla programistów Szybkie dostarczanie oprogramowania wysokiej jakości Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Menedżerowie produktu Jira Elastyczne zarządzanie projektami Confluence Wiedza, wszystkie informacje w jednym miejscu Jira Product Discovery NOWOŚĆ Rejestrowanie pomysłów i nadawanie im priorytetów Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Specjaliści IT Jira Service Management Dostarczanie usług z dużą prędkością Guard NOWOŚĆ Zwiększone bezpieczeństwo w chmurze Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Zespoły biznesowe Jira Elastyczne zarządzanie projektami Confluence Wiedza, wszystkie informacje w jednym miejscu Trello Porządkowanie i wizualizowanie pracy Loom NOWOŚĆ Szybkie, asynchroniczne aktualizacje wideo Jira Service Management Dostarczanie usług z dużą prędkością Customer Service Management Customer experiences reimagined Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Kadra zarządzająca Focus NOWOŚĆ Planowanie strategiczne w skali przedsiębiorstwa Talent NOWOŚĆ Planowanie zasobów ludzkich pod kątem wiedzy Jira Align Znaczenie i planowanie pracy w całym przedsiębiorstwie Pewna optymalizacja strategii i wyników Focus • Talent • Align Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Back Rozwiązania Rozwiązania Według przypadku użycia Współpraca zespołowa Strategia i planowanie Zarządzanie usługami Tworzenie oprogramowania Według zespołu Oprogramowanie Marketing IT Według rozmiaru Enterprise Małe firmy Startup Organizacje non-profit Według branży Handel detaliczny Telekomunikacja Usługi specjalistyczne Administracja publiczna Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Back Dlaczego Atlassian Dlaczego Atlassian System pracy Nowość Plan Atlassian dotyczący współpracy zespołów Narzędzia Integracji Tysiące aplikacji do połączenia z produktami Atlassian Klienci Studia przypadków i historyjki oparte na pracy zespołowej FedRAMP Zgodne rozwiązania dla sektora publicznego Odporność Wysoce wydajna struktura klasy korporacyjnej Platforma Nasza głęboko zintegrowana, niezawodna i bezpieczna platforma Centrum zaufania Bezpieczeństwo danych, zgodność z przepisami i dostępność Back Zasoby Zasoby Obsługa klienta Zadawaj pytania, zgłaszaj błędy i dziel się opinią Znajdź partnerów Skorzystaj z doradztwa, szkolenia i wsparcia w zakresie dostosowywania produktów Atlassian Ascend Zasoby i wsparcie ułatwiające transformację Społeczność Ucz się, łącz i rozwijaj ze społecznością Atlassian Wsparcie Pytania ogólne Doradztwo dotyczące produktu Wsparcie dla partnerów Wsparcie dla firm Wsparcie techniczne Ceny i płatności Wsparcie dla programistów Zakup licencji Zasoby Zarządzanie projektami Agile Atlassian Learning Rozpocznij korzystanie Współpraca nad projektem Podręcznik Team Playbook Dokumentacja produktu Back Enterprise Więcej + Mniej - Zacznij korzystać za darmo Jira Elastyczne zarządzanie projektami Jira Service Management Dostarczanie usług z dużą prędkością Confluence Wiedza, wszystkie informacje w jednym miejscu Zobacz wszystkie produkty Zacznij korzystać za darmo Back Zacznij korzystać za darmo Legal Legal information Impressum Impressum Impressum Serviceanbieter: Atlassian Pty Ltd Level 6, 341 George Street Sydney NSW 2000 Australien Tel: +61 2 9262 1443 E-Mail: legalfilings@atlassian.com Legal Representative: Stan Shepard Atlassian Pty Ltd ist ein Unternehmen, das nach australischem Recht gegründet und registriert ist. ACN: 102 443 916; ABN: 53 102 443 916; TFN: 796 192 619 USt-IdNr.: EU372001951 Service Provider: Atlassian Pty Ltd Level 6, 341 George Street Sydney NSW 2000 Australia Tel: +61 2 9262 1443 E-Mail: legalfilings@atlassian.com Legal Representative: Stan Shepard Atlassian Pty Ltd is a company incorporated and registered under Australian law. ACN: 102 443 916; ABN: 53 102 443 916; TFN: 796 192 619 VAT number: EU372001951 Related content Wytyczne dotyczące znaków towarowych Dowiedz się więcej Zgłaszanie naruszeń praw autorskich i znaków towarowych Dowiedz się więcej Third Party Code Policy Dowiedz się więcej Warunki i zasady dotyczące szkoleń Dowiedz się więcej Stay informed Subscribe to receive notifications from us about updates to our legal terms (including our legal policies) and our list of sub-processors. Sign up for updates Firma Kariera Wydarzenia Blogi Relacje z inwestorami Fundacja Atlassian Materiały prasowe Skontaktuj się z nami produkty Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Zobacz wszystkie produkty Zasoby Pomoc techniczna Zakup licencji Atlassian Community Baza wiedzy Marketplace Moje konto Utwórz zgłoszenie do pomocy technicznej Poznawanie Partnerzy Szkolenia i certyfikaty Dokumentacja Zasoby dla programistów Usługi Enterprise Zobacz wszystkie zasoby Copyright © 2025 Atlassian Polityka prywatności Warunki Nota prawna Wybierz język Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://git-scm.com/book/bg/v2/%d0%9a%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5-%d0%b2-Git-%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-%d0%bd%d0%b0-%d0%ba%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5%d1%82%d0%b5-%d0%ba%d0%be%d0%b4-%d0%b8-%d1%81%d0%bb%d0%b8%d0%b2%d0%b0%d0%bd%d0%b5%d1%82%d0%be | Git - Основи на клоновете код и сливането About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 3.2 Клонове в Git - Основи на клоновете код и сливането Основи на клоновете код и сливането Нека илюстрираме разклоняването и сливането с малък пример, какъвто може да срещнете в реалния живот. Ще следваме следните стъпки: Работите по уеб сайт. Създавате нов клон за нова статия, по която работите. Извършвате някакви дейности по този клон. В този момент, получавате обаждане за внезапно възникнал критичен проблем в друга част от сайта, който трябва да решите бързо. Ще направите следното: Превключвате към работния (production) клон. Създавате нов клон и решавате проблема в него. След тест, че всичко в поправката е наред, сливате hotfix клона обратно в работния клон. Превключвате отново към клона с новата статия и продължавате работа. Основи на разклоняването Първо, нека приемем, че работите по проекта си и вече имате няколко къмита в клона master . Фигура 18. Проста история на къмитите Решили сте, че трябва да работите по проблем #53 в issue-tracking системата, която ползва вашата компания. За да създадете клон и превключите към него в същия момент, изпълнете командата git checkout с параметър -b : $ git checkout -b iss53 Switched to a new branch "iss53" Това е съкратена версия на командите: $ git branch iss53 $ git checkout iss53 Фигура 19. Създаване на нов указател към branch Вие си работите по сайта и правите няколко къмита. По време на този процес, клонът iss53 се премества напред, защото е текущ (това означава, че HEAD указателят сочи към него): $ vim index.html $ git commit -a -m 'Create new footer [issue 53]' Фигура 20. Клонът iss53 се е преместил напред в процеса на работа Сега получавате обаждане, че нещо не е наред с уебсайта и трябва да го оправите незабавно. С Git, не е нужно да прилагате поправката заедно с промените, които се съдържат в iss53 клона и не е нужно да влагате усилия по отмяната на тези промени преди да можете да приложите спешната поправка в production версията на сайта. Всичко, което трябва да направите е да превключите обратно към master клона. Обаче преди да направите това, отбележете, че ако работната ви директория или индексната област съдържат некъмитнати промени, които влизат в конфликт с клона, към който превключвате, Git няма да позволи превключването на клоновете. Най-добре е да имате чист работен статус преди превключването. Съществуват начини да заобиколите това (известно като stashing и commit amending), които ще разгледаме по-късно в Stashing и Cleaning . Засега, нека приемем, че сте къмитнали промените си, така че може да се върнете в master клона: $ git checkout master Switched to branch 'master' В този момент, работната ви директория ще се превърти обратно до съдържанието, което е имала преди да започнете работа по проблем 53 и можете да се концентрирате в спешната поправка, която е необходимо да въведете. Това е важен момент за запомняне: когато превключвате между клоновете, Git връща работната директория до статуса, в който е била последния път, когато сте къмитнали в този клон. Системата добавя, изтрива и променя файловете автоматично, за да ви предостави работното копие на обектите в момента на последния ви къмит. След това, имате да правите спешната поправка. Нека създадем един hotfix клон, по който да работим докато тя стане готова: $ git checkout -b hotfix Switched to a new branch 'hotfix' $ vim index.html $ git commit -a -m 'Fix broken email address' [hotfix 1fb7853] Fix broken email address 1 file changed, 2 insertions(+) Фигура 21. Hotfix клон произлизащ от master клона Можете да пускате тестовете си, да се уверите, че поправката работи както се очаква и да слеете обратно вашия hotfix клон в master клона за да го пуснете в работния вариант. Това се прави с командата git merge : $ git checkout master $ git merge hotfix Updating f42c576..3a0874c Fast-forward index.html | 2 ++ 1 file changed, 2 insertions(+) В съобщението от сливането ще забележите фразата “fast-forward”. Понеже къмитът C4 , към който сочи клона hotfix , който сляхте, беше директно след къмита C2 , Git просто премества указателя напред. Казано по друг начин, когато се опитвате да слеете един къмит с друг такъв, който може да бъде достигнат следвайки историята на първия, Git опростява нещата премествайки указателя напред, защото не се налага да се върши работа по сливане на разклонен код. Това се нарича “fast-forward.” Сега промяната ви е в snapshot-а на къмита сочен от master клона и можете да пуснете промяната в реалния сайт. Фигура 22. master е превъртян (fast-forwarded) към hotfix След като суперважната промяна е въведена, можете да се върнете обратно към работата, която вършехте преди обаждането. Обаче, първо ще изтриете клона hotfix , понеже вече не ви е нужен — master клонът сочи към същото място. Изтриването се прави с параметъра -d на командата git branch : $ git branch -d hotfix Deleted branch hotfix (3a0874c). Сега можете да се прехвърлите към клона, в който си вършите обичайната работа по проблем 53 и да си я продължите. $ git checkout iss53 Switched to branch "iss53" $ vim index.html $ git commit -a -m 'Finish the new footer [issue 53]' [iss53 ad82d7a] Finish the new footer [issue 53] 1 file changed, 1 insertion(+) Фигура 23. Работата продължава в клона iss53 Тук си струва да отбележим, че промените, които направихте в клона hotfix не се съдържат във файловете на клона iss53 . Ако искате да ги имате, можете да слеете master клона в iss53 изпълнявайки git merge master , или пък можете да изчакате с интегрирането на тези промени докато дойде момента, в който решите че е време да слеете iss53 клона обратно в master . Сливане Да кажем, че сте решили, че работата по проблем 53 е свършена и сте готови да я слеете в master клона. За да направите това, ще действате по същия начин, по който го направихте с клона hotfix по-рано. Всичко, което трябва да направите е да превключите към клона, в който искате да сливате и да изпълните git merge : $ git checkout master Switched to branch 'master' $ git merge iss53 Merge made by the 'recursive' strategy. index.html | 1 + 1 file changed, 1 insertion(+) Това обаче изглежда по-различно от hotfix сливането. В този случай, историята на разработката се е отклонила от по-ранна точка. Понеже къмитът на клона, в който сте (С4), не е директен предшественик на клона, който сливате, Git ще има малко работа за вършене. В този случай, Git прави просто трипосочно сливане използвайки двата snapshot-а на клоновете и общия им предшественик (С2). Фигура 24. Три snapshot-а използвани в типично сливане Това се нарича сливащ къмит (merge commit) и е специален заради това, че има повече от един родител. Вместо просто да премести указателя на клона напред, Git създава нов snapshot, който е резултат от това трипосочно сливане и автоматично създава нов къмит, който да сочи към него. Фигура 25. Сливащ commit Сега, когато работата ви е слята, вече не се нуждаете от клона iss53 . Можете да затворите проблема в issue-tracking системата и да изтриете клона: $ git branch -d iss53 Конфликти при сливане Понякога обаче, сливането не минава гладко. Ако сте променили една и съща част от един и същи файл в различни клонове, които искате да слеете, Git няма да може да направи това чисто. Ако промените ви по проблем #53 са модифицирали една и съща част от файл с тези от клона hotfix , ще се получи конфликт при сливането, съобщението за който може да изглежда по подобен начин: $ git merge iss53 Auto-merging index.html CONFLICT (content): Merge conflict in index.html Automatic merge failed; fix conflicts and then commit the result. Git не е извършил merge къмита. Процесът е прекъснат докато не разрешите конфликта Ако искате да видите кои файлове не са слети вследствие на конфликта, можете да изпълните git status : $ git status On branch master You have unmerged paths. (fix conflicts and run "git commit") Unmerged paths: (use "git add <file>..." to mark resolution) both modified: index.html no changes added to commit (use "git add" and/or "git commit -a") Всичко, по което има конфликти при сливането се показва като unmerged. Git добавя стандартни маркери за разрешаване на конфликта към файловете, в които има такъв, така че можете да ги отворите ръчно и да ги коригирате. Файлът ви ще съдържа секция подобна на тази: <<<<<<< HEAD:index.html <div id="footer">contact : email.support@github.com</div> ======= <div id="footer"> please contact us at support@github.com </div> >>>>>>> iss53:index.html Това означава, че версията в HEAD (вашият master клон, понеже той е текущия, в който сте изпълнили командата по сливането) е горната част на този блок (всичко преди ======= ), докато версията в клона iss53 е в долната част. За да решите конфликта, трябва да изберете една от двете или да слеете съдържанието сами. Например, можете да замените целия блок с това: <div id="footer"> please contact us at email.support@github.com </div> Това решение съдържа по малко от всяка секция и редовете <<<<<<< , ======= , >>>>>>> се изтриват напълно. След като направите това за всяка секция и всеки файл в който има конфликти, изпълнете git add за всеки файл, за да го маркирате като коригиран. Индексирането на файл в Git го маркира като коректен, без конфликти. Ако желаете да използвате графичен инструмент за решаването на конфликти, можете да изпълните git mergetool , което ще стартира подходящия визуален инструмент и ще ви води през конфликтите подред: $ git mergetool This message is displayed because 'merge.tool' is not configured. See 'git mergetool --tool-help' or 'git help config' for more details. 'git mergetool' will now attempt to use one of the following tools: opendiff kdiff3 tkdiff xxdiff meld tortoisemerge gvimdiff diffuse diffmerge ecmerge p4merge araxis bc3 codecompare vimdiff emerge Merging: index.html Normal merge conflict for 'index.html': {local}: modified file {remote}: modified file Hit return to start merge resolution tool (opendiff): Ако желаете да използвате инструмент различен от подразбиращия се (в случая Git е избрал opendiff , защото командата е пусната на Mac), можете да видите всички поддържани такива в горната част на изхода от командата след надписа “one of the following tools.” Просто напишете името на инструмента, който предпочитате. Забележка Ако се нуждаете от по-модерни инструменти за разрешаване на заплетени конфликти, обръщаме повече внимание на това в Сливане за напреднали . След като затворите инструмента, Git ви пита дали сливането е успешно. Ако кажете това на скрипта, системата ще индексира файла и ще го маркира като коректен. Можете да пуснете git status отново за да проверите дали всички конфликти са разрешени: $ git status On branch master All conflicts fixed but you are still merging. (use "git commit" to conclude merge) Changes to be committed: modified: index.html Ако това ви устройва и сте проверили, че всичко по което е имало конфликти е в индекса, можете да изпълните git commit за да завършите сливащия къмит. Къмит съобщението по подразбиране изглежда подобно на това: Merge branch 'iss53' Conflicts: index.html # # It looks like you may be committing a merge. # If this is not correct, please remove the file # .git/MERGE_HEAD # and try again. # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # All conflicts fixed but you are still merging. # # Changes to be committed: # modified: index.html # Ако мислите, че за другите ви колеги гледащи кода по-късно ще е полезно да разберат как сте разрешили конфликта, можете да промените къмит съобщението с обяснение за това. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/fr/software/jira/service-management/retail-ecommerce | Jira Service Management pour les entreprises de vente au détail et d'e-commerce Close Afficher cette page dans votre langue ? Toutes les langues Sélectionner votre langue 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Télécharger gratuitement Fonctionnalités Solutions Par cas d’usage Par capacité Par secteur Par cas d’usage Support informatique Opérations informatiques Équipes métier Service client Ressources humaines Par capacité Petites équipes Premium Enterprise Par secteur Technologie et télécommunications Services financiers Commerce Fabrication Back Tarifs Ressources Par type ITSM Guide produit Modèles Ressources supplémentaires Back Plus + Moins - Télécharger gratuitement Back Télécharger gratuitement Améliorez votre support pour la vente au détail et l'e-commerce grâce à Jira Service Management Les entreprises de vente au détail et d'e-commerce utilisent Jira Service Management pour garder une longueur d'avance sur la concurrence grâce à une expérience basée sur l'IA qui améliore la satisfaction du support, évolue efficacement et protège les données de leurs clients. Essayer gratuitement Assister à une démo Modernisez vos services de vente au détail Réunissez vos équipes sur une plateforme personnalisable, optimisée par l'IA qui intègre le feedback client sur l'ensemble des canaux de vente au détail afin de simplifier les processus et les workflows. Donnez à vos employés les moyens d'accéder à des données en temps réel sur l'inventaire, les ventes et le comportement des clients sur tous les canaux opérationnels. En savoir plus Augmentez la satisfaction client Les équipes opérationnelles de vente au détail peuvent résoudre les tickets plus rapidement et améliorer leur score de satisfaction client en collaborant sur une seule plateforme. Les équipes peuvent utiliser l'IA pour évaluer le sentiment des clients et répondre rapidement aux demandes , aux incidents et aux changements . Développez efficacement votre activité d'e-commerce Dans un monde où les marchés sont de plus en plus compétitifs, la rapidité et la qualité du service sont indispensables. Fournissez à vos clients un service de vente au détail en ligne efficace en utilisant une configuration basée sur l'IA et des formulaires, des workflows ainsi que des automatisations sans code. En savoir plus Protégez les données de vos clients Dans un secteur où sont gérées des informations et des données sensibles sur les clients, il est vital que les entreprises de vente au détail et d'e-commerce maintiennent leurs technologies à jour, garantissent la confidentialité et se conforment à la réglementation. Sécurité Atlassian Fonctionnalités de Jira Service Management pour les entreprises de vente au détail et d'e-commerce Explorer toutes les fonctionnalités Gestion des demandes Le support omnicanal de l'agent de service virtuel, optimisé par l'IA, permet d'apporter une aide rapide au moment et à l'endroit où vos clients en ont besoin. Gestion des actifs Gérez efficacement l'inventaire, suivez la propriété et les cycles de vie, et réduisez les coûts. Workflows automatisés Utilisez l'IA pour créer rapidement des automatisations qui simplifient vos workflows, par exemple en reliant les tickets Jira connexes ou en assignant automatiquement des tickets. Gestion de la configuration Gagnez en visibilité sur l'infrastructure qui prend en charge les apps et services critiques. Cernez les dépendances des services afin de réduire les risques. Respectez vos SLA Répondez en premier aux besoins importants des clients grâce aux files d'attente priorisées. Utilisez l'IA pour trier, répondre et résoudre les demandes rapidement. Réagissez rapidement en cas d'incident Réunissez vos équipes de développement, de support et opérationnelles et utilisez les fonctionnalités de l'AIOps pour répondre rapidement, résoudre les incidents et en tirer des leçons. En savoir plus sur l'approche Atlassian de la gestion des services Lire le guide Modèles Des modèles de service client et d'ITSM qui vous aident à vous lancer rapidement Donnez aux bonnes personnes le contexte dont elles ont besoin pour agir. Gérez les demandes, les incidents et les changements pour fournir d'incroyables services, rapidement. Vous pouvez également essayer notre configuration de projet basée sur l'IA pour créer des types de demandes, des champs de formulaire et des automatisations personnalisés. Explorer les modèles Support du Virtual Service Agent Support en continu optimisé par l'IA Renforcez votre service omnicanal grâce à un agent de service virtuel qui gère les interactions avec l'assistance à l'aide de l'IA. Créez des flux de conversation personnalisés pour automatiser des actions telles que la réinitialisation des mots de passe, ou puisez dans votre base de connaissances existante pour répondre aux demandes les plus courantes. Libérez du temps aux agents tout en apportant de l'aide au moment et à l'endroit où vos clients en ont besoin. En savoir plus Plus de 50 000 entreprises font confiance à Jira Service Management « Depuis le lancement, nous avons obtenu un score de satisfaction de 4,9/5 en moyenne, ce qui est fantastique. En ce qui concerne la solution précédente, nous ne recevions que des plaintes. » Rob Crompton, Head of Service Management, The Very Group « Grâce à Jira Service Management, nous devenons plus agiles. Cette solution tout-en-un efficace nous permet de suivre ce qui se passe, de connaître la direction que chacun doit prendre et d'améliorer nos opérations. » VICE-PRÉSIDENT ADJOINT, client Atlassian du secteur de la vente au détail ← → Découvrez pourquoi tant de personnes font confiance à notre logiciel primé Atlassian a été reconnu parmi les leaders du secteur dans le Magic Quadrant™ 2022 de Gartner® pour les plateformes de gestion des services informatiques . En savoir plus sur l'étude Total Economic Impact™ de Jira Service Management d'Atlassian . Découvrez les résultats de Jira Service Management dans le rapport « Gartner Peer Insights ». Gestion des services optimisé par l'IA pour la vente au détail et l'e-commerce Choisissez Jira Service Management pour proposer des expériences de service exceptionnelles et accélérer le flux de travail. Essayer gratuitement Entreprise Carrières Événements Blogs Relations avec les investisseurs Atlassian Foundation Kit pour la presse Nous contacter Index de l'égalité professionnelle produits Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Voir tous les produits Ressources Support technique Achats et licences Communauté Atlassian Base de connaissances Marketplace Mon compte Créer un ticket de support Apprendre Partenaires Formation et certification Documentation Ressources développeurs Services Enterprise Découvrir toutes les ressources Copyright © 2025 Atlassian Politique de confidentialité Conditions Mentions légales Choisir la langue Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://www.atlassian.com/ru/software/jira/service-management/product-guide/getting-started/quick-start-guide | Краткое руководство по началу работы Jira Service Management Cloud Close Хотите открыть эту страницу на своем языке ? Все языки Выберите язык 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Получить бесплатно Функции Решения По варианту использования По возможностям По отрасли По варианту использования Служба ИТ-поддержки ИТ-операции Бизнес-команды Служба поддержки клиентов Отдел кадров По возможностям Небольшие команды Premium Enterprise По отрасли Технологии и телекоммуникации Финансовые услуги Розничная торговля Производство Back Цены Ресурсы По типу ITSM Руководство по продукту Шаблоны Дополнительные ресурсы Back Дополнительно + Меньше - Получить бесплатно Back Получить бесплатно Главная страница с руководствами О Jira Service Management Начало работы Краткое руководство по началу работы Управление заявками на обслуживание Управление инцидентами Управление проблемами Управление изменениями Управление сервисами Enterprise Управление знаниями Управление ресурсами и конфигурацией Советы и рекомендации Руководство по функциям ИИ Руководство по функции «Аналитика» Руководство по функции «Активы» Руководство по функции «Автоматизация» Руководство по функции чата Руководство по функции форм Руководство по возможностям Virtual Service Agent Руководство по адаптации агентов Руководство по интеграции с Jira Руководство по адаптации к тарифному плану Premium Руководство по проектам команды Управление кадровыми услугами Краткое руководство по началу работы Введение Это руководство предназначено для всех, кто настраивает свой первый проект службы поддержки в Jira Service Management. Если вы еще не зарегистрировались для использования Jira Service Management, сделайте это бесплатно . Войдя в Jira Service Management, вы сможете настроить все параметры с помощью подсказок. Если вам нужна дополнительная помощь или вы просто хотите увидеть всю информацию в одном месте, прежде чем браться за дело, это руководство для вас. Обратите внимание, что это руководство создано специально для администраторов проектов Jira Service Management. Если вы агент Jira Service Management, ознакомьтесь с нашим руководством по адаптации агентов . Шаг 1. Создание и настройка проекта Создание проекта службы поддержки В Jira Service Management множество шаблонов проектов, с помощью которых можно быстро выполнять настройку и создавать проекты, адаптированные к потребностям конкретной команды или области применения. Эти шаблоны включают предварительно настроенные типы запросов, рабочие процессы и другие полезные возможности. Доступны шаблоны для управления ИТ-службами и обслуживанием клиентов, а также ряд шаблонов для бизнес-команд, таких как отдел кадров, финансовый отдел и отдел маркетинга. Подробнее о шаблонах проектов в Jira Service Management Чтобы создать проект службы поддержки, выполните следующие действия: В верхней строке меню выберите Projects (Проекты), затем нажмите Create project (Создать проект). Просмотрите доступные шаблоны в категории Service management (Управление службами) и выберите тот, который лучше всего соответствует вашим потребностям. Просмотрите сведения о шаблоне. Если он вас устраивает, нажмите Use template (Использовать шаблон). А если вы выбрали пустой шаблон, нажмите Create blank project (Создать пустой проект). Выберите тип проекта: проект команды или проект компании . (Примечание: проект команды доступен только в определенных шаблонах проектов.) Укажите название проекта. Создайте ключ проекта или используйте сгенерированный ключ. Выберите тип команды, которая будет работать с проектом. Эти данные можно будет изменить позже в настройках проекта. Настройте доступ к каналу, чтобы определить, кто сможет отправлять запросы в этот проект. Если вы хотите использовать настройки существующего проекта, укажите его название. Если шаблон проекта доступен в обоих типах проектов, проверьте выбранный тип. Если выбран проект команды, ознакомьтесь с разделами настроек Access (Доступ) и Default language (Язык по умолчанию). Выберите Create project (Создать проект). Настройка центра поддержки и портала Клиенты обращаются за помощью в центр поддержки и на порталы. Важно настроить единый фирменный стиль пользовательского интерфейса, где клиенты будут видеть всю необходимую информацию. Настройка центра поддержки Начнем с центра поддержки. На каждом сайте Jira Service Management есть онлайн-центр поддержки. Кроме того, в каждом проекте службы поддержки есть портал. В центре поддержки клиенты могут просматривать все порталы проекта службы поддержки, к которым у них есть доступ, отправлять запросы, а также искать информацию во встроенной базе знаний, чтобы решать возникающие проблемы самостоятельно. Ниже кратко описываются ключевые параметры центра поддержки, которые можно настроить. Сообщение на странице входа Добавьте сообщение на страницу входа, чтобы поприветствовать своих клиентов или помочь им выполнить вход. Подробнее Объявления Объявления на главной странице центра поддержки информируют клиентов о важных новостях или проблемах, связанных со службами. Подробнее Внешний вид системы Настройка внешнего вида центра поддержки, включая следующие элементы. Название центра поддержки Заголовок главной страницы логотип Баннер Цвета фона баннера, ссылок и кнопок Цвет текста баннера для центра поддержки Подробнее Макет главной страницы Настройка представления порталов в центре поддержки. Сгруппируйте и представьте на экране избранные порталы, чтобы клиентам было проще найти нужные сведения. Оставшиеся порталы можно отсортировать по популярности или названию. Подробнее Чтобы изменить любой из вышеперечисленных параметров, выполните следующие действия: Перейдите в раздел Settings > Products (Настройки > Продукты). На боковой панели выберите Configuration (Конфигурация) в разделе Jira Service Management . В разделе Customize your help center (Настройка центра поддержки) появится список доступных опций настройки. Выберите нужную опцию, внесите изменения и выберите Save changes (Сохранить изменения). Подробнее о настройке центра поддержки Настройка порталов для проекта службы поддержки Каждый проект службы поддержки поставляется с онлайн-порталом, через который клиенты взаимодействуют с сервисной командой. Порталы размещаются в центре поддержки, чтобы клиенты могли обращаться за помощью к любой команде в организации из единого центра. Как и в случае с центром поддержки, вы можете изменить название портала, обратиться к клиентам с приветственным словом и добавить логотип компании, чтобы портал отражал ваш бренд. Чтобы настроить порталы, выполните следующие действия. На боковой панели проекта службы поддержки выберите Project settings > Portal settings (Настройки проекта > Настройки портала). При необходимости измените поля Name (Название), Introduction text (Текст приветствия) и Logo (Логотип). Логотип будет отображаться в уведомлениях вашего проекта службы поддержки. Цвета заголовка, URL-адресов и кнопок на портале наследуются из центра поддержки. Подробнее о настройке центра поддержки и порталов Настройка адреса электронной почты для проекта службы поддержки Проект службы поддержки поставляется с предварительно настроенным адресом электронной почты в облаке. Этот адрес можно отправить клиентам, чтобы они сразу же начали им пользоваться. Можно также добавить собственный адрес электронной почты для привязки существующего аккаунта (например, адрес электронной почты, который ИТ-команда использует для входящих запросов). Чтобы добавить собственный аккаунт электронной почты для входящих запросов, выполните следующие действия: На боковой панели проекта службы поддержки выберите Project Settings > Email requests (Настройки проекта > Запросы по электронной почте). Выберите поставщика услуг электронной почты в разделе Connect a custom email account (Подключить пользовательский аккаунт электронной почты) и следуйте инструкциям по привязке аккаунта. Подробнее о получении запросов по электронной почте Шаг 2. Настройка типов запросов и очередей Настройка типов запросов Типы запросов помогают определять входящие запросы и разбивать их по категориям, а также собирать информацию, необходимую для их обработки. В вашем проекте службы поддержки есть типы запросов по умолчанию, основанные на шаблоне, который использовался при создании проекта. Вы можете изменить эти типы запросов и добавить другие в соответствии с потребностями клиентов и команды. Типы запросов можно объединить в группы портала, чтобы клиентам было проще получить поддержку. Ниже приведен пример портала службы поддержки для отдела кадров с типами запросов на ориентацию, адаптацию, увольнение, внутренние переводы, обучение сотрудников и другие действия. Чтобы создать новый тип запроса, выполните следующие действия: На панели навигации слева выберите Project settings (Настройки проекта), затем нажмите Request types (Типы запросов). Выберите Create request type (Создать тип запроса). Здесь можно нажать Create custom (Создать пользовательский элемент), чтобы создать собственный тип запроса, или Create from template (Создать элемент из шаблона), чтобы задействовать шаблоны, разработанные для разных команд и сценариев использования, и с их помощью быстро создать новый тип запроса, который можно будет отредактировать позже. Создание пользовательского элемента Нажмите Create custom (Создать пользовательский элемент). Укажите имя, описание, значок и тип задачи для типа запроса, затем нажмите кнопку Next (Далее). Выберите группу портала, создайте новую группу или не устанавливайте флажок, чтобы скрыть этот тип запроса на портале, а затем нажмите кнопку Create (Создать). Создание элемента из шаблона Изучите каталог либо выполните поиск и предварительный просмотр различных шаблонов. Нажмите Select (Выбрать), чтобы выбрать шаблон, который нужно использовать при создании нового типа запроса. Просмотрите и обновите сведения о типе запроса, включая имя, описание, значок, группу портала, тип задачи и связанный рабочий процесс, затем нажмите Save (Сохранить). Выполнив действия, связанные с одним из двух приведенных методов, вы создадите объект типа запроса, связанный с выбранным типом задачи и рабочим процессом. Затем нужно выбрать поля, которые будут видны клиентам и агентам. У вас есть возможность настроить отображение полей с учетом типа запроса, чтобы собирать только ту информацию, которая нужна команде для успешного выполнения работы. Чтобы изменить тип запроса, включая набор полей, доступных в представлениях для агентов и клиентов, выполните следующие действия. На панели навигации слева выберите Project settings (Настройки проекта), затем нажмите Request types (Типы запросов). Выберите тип запроса, который нужно изменить. Перейдите на вкладку Request form (Форма запроса). Здесь можно выбрать поля, которые будут видны пользователям, обращающимся за поддержкой, и которые они будут заполнять при создании запроса на портале. Добавьте новые поля, перетащив их с панели справа, выполните поиск среди уже используемых на сайте полей или создайте новое пользовательское поле. Можно снабжать поля инструкциями, отмечать их как обязательные и назначать им предустановленные значения. Чтобы найти и прикрепить существующие формы к типу запроса, нажмите Add form (Добавить форму), выберите нужную форму из раскрывающегося списка, а затем нажмите Add (Добавить). Если форм нет, перейдите в раздел Project settings (Настройки проекта), а затем в подраздел Forms (Формы), чтобы создать нужные формы. На вкладке Work item view (Представление задачи) можно выбрать поля, которые будут видны только агентам, а также поля, которые будут отображаться в форме запроса у пользователей, обращающихся за поддержкой. Добавьте новые поля, перетащив их с панели справа, выполните поиск среди уже используемых на сайте полей или создайте новое пользовательское поле. Кроме того, при необходимости можно изменить порядок полей или перетащить поля в раздел Hidden when empty (Скрыть, если не заполнено), чтобы отрегулировать представление задачи для агентов. Примечание. В проектах компании каждый тип запроса связан с типом задачи. Типы задач могут использоваться одновременно в разных проектах на сайте Jira. Доступные поля и рабочие процессы в типе запроса зависят от полей и рабочих процессов в соответствующем типе задачи . Каждый проект команды имеет собственные типы запросов, которые не могут использоваться в других проектах. Это означает, что в каждом проекте команды имеются собственные типы запросов, которые не зависят от других проектов и не связаны с типом задачи. Подробнее о группировании запросов клиентов по типам запросов Чтобы изменить рабочий процесс для типа запроса, выполните следующие действия. На панели навигации слева выберите Project settings (Настройки проекта), затем нажмите Request types (Типы запросов). Выберите меню других действий рядом с типом запроса, который нужно обновить. Чтобы отредактировать рабочий процесс, нажмите View and edit workflow (Просмотреть и отредактировать рабочий процесс). Выберите пункт Edit workflow (Редактировать рабочий процесс), внесите изменения и нажмите Publish (Опубликовать). Чтобы заменить рабочий процесс, в разделе Workflow (Рабочий процесс) выполните следующие действия. Нажмите Replace using template (Заменить с использованием шаблона). Вы сможете создать новый предварительно настроенный рабочий процесс на основе шаблона и связать его с типом запроса. Воспользуйтесь функцией Preview (Предварительный просмотр) для шаблона, чтобы открыть его описание, а также сведения о статусах и переходах. Нажмите Select (Выбрать), чтобы выбрать шаблон, который нужно использовать, затем просмотрите его и введите имя нового рабочего процесса и типа задачи. Нажмите Continue (Продолжить). Новый рабочий процесс и тип задачи будут добавлены в проект и связаны с обновляемым типом запроса. Либо нажмите Replace with existing (Заменить существующим элементом). Выберите рабочий процесс, который нужно использовать, затем нажмите Update (Обновить). Эти возможности редактирования и замены рабочего процесса также доступны на экране конфигурации конкретного типа запроса. Нажмите Manage workflow (Управление рабочим процессом), затем выберите нужный вариант. Настройка очередей Когда клиенты проекта службы поддержки создают запрос, он попадает в очередь в виде задачи. Очереди помогают автоматически сортировать задачи по приоритету, упорядочивать их представление для команды и выделять задачи, над которыми команда должна работать в первую очередь в соответствии с SLA . Команда может видеть количество задач в каждой очереди и переключаться между очередями для своевременного выполнения задач. Jira Service Management поставляется с очередями по умолчанию. Администраторы проекта могут их изменить и привести в соответствие с тем, как команды расставляют приоритеты и обрабатывают запросы клиентов. Чтобы получить доступ к очередям, выполните следующие действия: На боковой панели проекта службы поддержки перейдите в раздел Queues (Очереди). Для переключения между очередями выбирайте их на боковой панели. Создание групп очередей Очереди можно объединить в три труппы, чтобы поддерживать порядок в рабочем пространстве: Starred (Отмеченные очереди). Можно отметить часто используемые очереди, чтобы быстро получать к ним доступ из проекта службы поддержки. Отмеченные очереди отображаются только в вашем представлении и не влияют на работу команды. Team priority (Приоритетные очереди команды). Это критически важные для бизнеса очереди, которые агенты должны видеть в любое время. Other (Прочие). Очереди в этой группе свернуты, но агенты могут отмечать их, чтобы закрепить на месте. Чтобы упорядочить очереди, выполните следующие действия: На боковой панели проекта службы поддержки перейдите в раздел Queues (Очереди). Выберите Manage queues (Управление очередями). Путем перетаскивания разделите очереди на две группы: Team priority (Приоритетные очереди команды) и Other (Прочие). Выберите Close (Закрыть). Чтобы пометить очередь, просто наведите на нее курсор и выберите значок звездочки Создание новой очереди Как упоминалось ранее, Jira Service Management поставляется с набором готовых очередей для команды. Вы можете отредактировать очереди по умолчанию , чтобы настроить отображение задач с учетом своих предпочтений. Кроме того, в Jira Service Management вы можете создать собственные очереди в соответствии со своими потребностями. Эти очереди можно использовать для отображения определенных запросов в зависимости от их типа, статуса или более конкретных критериев, заданных оператором Jira Query Language (JQL) . Чтобы создать новую очередь, выполните следующие действия: На боковой панели проекта службы поддержки перейдите в раздел Queues (Очереди). Выберите Manage queues (Управление очередями) на боковой панели навигации. Выберите Create new queue (Создать очередь). Введите имя очереди. В разделе Filter by (Фильтр) выберите тип, статус, решение и метку задачи из раскрывающихся меню. Можно также выбрать Advanced (Расширенный) и ввести оператор JQL . При необходимости выберите критерии из раскрывающегося меню More (Еще). При необходимости выберите порядок сортировки из раскрывающегося меню Order by (Сортировка). В разделе Columns (Столбцы) расположите столбцы в нужном порядке путем перетаскивания. В этом порядке столбцы будут отображаться в очереди. Выберите Create (Создать). Подробнее о сортировке запросов клиентов для агентов с помощью очередей Шаг 3. Добавление участников команды и клиентов в проект службы поддержки Добавление в проект участников команды Пора пригласить других! Проект настроен, теперь нужно пригласить участников команды. Для этого добавьте каждого участника команды в проект службы поддержки в качестве агента. Чтобы добавить участников команды, выполните следующие действия: На боковой панели проекта службы поддержки перейдите в раздел Invite team (Пригласить команду). Введите адреса электронной почты пользователей, которых необходимо добавить в качестве агентов. Выберите Invite (Пригласить). Агентам будет присвоена роль Service Project Team (Команда проекта службы поддержки) и будут отправлены электронные сообщения со ссылкой на проект службы поддержки. Добавление в проект клиентов Теперь добавим клиентов в созданную службу поддержки. Клиенты — это пользователи, которые обращаются за помощью к вашему проекту службы поддержки. Необязательно сразу добавлять клиентов в проект службы поддержки, но важно научиться это делать. Добавлять клиентов в проект службы поддержки могут администраторы и агенты проекта службы поддержки. Чтобы добавить клиентов, выполните следующие действия: На боковой панели проекта службы поддержки перейдите в раздел Customers (Клиенты). Выберите Add customers (Добавить клиентов). Введите адрес электронной почты клиента. Чтобы добавить несколько клиентов за один раз, разделяйте их адреса запятыми. Добавьте клиента в организацию (необязательно). Выберите Add (Добавить). Клиенты получат электронное письмо с приглашением. Чтобы просмотреть или изменить письмо с приглашением, перейдите в раздел уведомлений клиентов . Можно настроить Jira Service Management таким образом, чтобы клиенты могли добавлять себя сами. Или же можно открыть проект службы поддержки для пользователей Jira. Подробнее о правах доступа клиентов . Теперь, когда основные настройки выполнены, вы можете вывести проект на новый уровень, воспользовавшись полезными практическими руководствами, обучающими материалами и документацией из нашей подборки. Вас ждет много интересного… Ознакомьтесь с нашей демонстрацией Jira Service Management по запросу . Вы сможете выбрать интересующие вас возможности и просмотреть индивидуальную демонстрацию. Ознакомьтесь с другими руководствами по продуктам Jira Service Management , в которых можно найти все: от основ до подробного описания методов. Загрузите Jira Service Management для мобильных устройств , чтобы предоставлять великолепное обслуживание на ходу. О Jira Service Management Обзор Читать руководство Начало работы Управление заявками на обслуживание Читать руководство Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Свяжитесь с нами продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы Enterprise Смотреть все ресурсы © Atlassian, 2025 г. Политика конфиденциальности Условия использования Impressum Выберите язык Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://git-scm.com/book/ru/v2/%d0%a0%d0%b0%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%b5%d0%bb%d1%91%d0%bd%d0%bd%d1%8b%d0%b9-Git-%d0%a3%d1%87%d0%b0%d1%81%d1%82%d0%b8%d0%b5-%d0%b2-%d0%bf%d1%80%d0%be%d0%b5%d0%ba%d1%82%d0%b5 | Git - Участие в проекте About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 5.2 Распределённый Git - Участие в проекте Участие в проекте Как именно участвовать в проекте — описать сложно, так как существует очень много различных вариаций как это делать. Так как Git очень гибок, люди могут и работают вместе по-разному. Отсюда и проблема описания участия в проекте — все проекты разные. Переменными здесь являются: количество активных участников, выбранный рабочий процесс, права доступа и, возможно, метод организации внесения вклада в проект извне. Первая переменная — количество активных участников — подразумевает количество пользователей, которые активно отправляют свой код в проект и как часто они это делают. В большинстве случаев у вас два или три разработчика, которые делают по несколько коммитов в день или меньше, если речь идёт о вялотекущих проектах. В больших компаниях или проектах количество разработчиков может исчисляться тысячами с сотнями тысяч коммитов в день. Это очень важно, так как при увеличении количества разработчиков вы сталкиваетесь со всё большим количеством проблем, связанных со встраиванием или слиянием нового кода. Изменения, которые вы отправляете, могут быть признаны устаревшими или быть серьёзно затронутыми уже применёнными изменениями, пока ваши ожидали одобрения. Как в таком случае можно быть уверенным, что ваш код консистентен и актуален, а ваши коммиты валидны? Следующая переменная — это используемый рабочий процесс. Централизован ли рабочий процесс и обладают ли все разработчики одинаковыми правами на запись в основную ветку разработки? Существует ли менеджер по интеграции или сопровождающий, кто проверяет все патчи? Все ли патчи проверяются другими разработчиками и проходят одобрение? Вы вовлечены в этот процесс? Существует ли лейтенант, которому следует отправить изменения прежде, чем в основной репозиторий? Следующая проблема — это уровень доступа. Рабочий процесс, используемый для участия в проекте, может сильно отличаться в зависимости от того, есть ли у вас доступ на запись или нет. Если у вас нет доступа на запись, то как проект принимает изменения? Существует ли вообще политика принятия изменений? Как много изменений вы вносите за раз? Как часто вы это делаете? Все эти вопросы могут повлиять на эффективность вашего участия в проекте, а так же на то, какие рабочие процессы наиболее предпочтительны или доступны для вас. Мы рассмотрим аспекты каждого из них на примере реальных ситуаций, переходя от более простых к более сложным. На основе этих примеров вы сможете создать реальные рабочие процессы применимые на практике. Правила создания коммитов Прежде чем мы начнём рассматривать конкретные варианты использования, давайте вспомним о сообщениях к коммитам. Наличие чётких рекомендаций по созданию коммитов и их соблюдение делают работу с Git и взаимодействие с другими гораздо проще. Проект Git предоставляет документ, в котором содержится ряд полезных советов по созданию коммитов для отправки патчей — вы можете ознакомиться с ними, прочитав файл Documentation/SubmittingPatches , находящийся в исходных кодах Git. Для начала, вам не следует отправлять ненужные пробелы. Git предоставляет простой способ проверки — перед коммитом выполните команду git diff --check , которая выведет список ненужных пробелов. Рисунок 56. Вывод команды git diff --check Выполняя эту команду перед коммитом вы сможете избежать отправки ненужных пробелов, которые могут раздражать других разработчиков. Далее, постарайтесь делать коммит логически разделённого набора изменений. Если возможно, попытайтесь делать ваши изменения легко понятными — не нужно писать код все выходные, работая над пятью разными задачами, а в понедельник отправлять результат как один большой коммит. Даже если вы не делали коммиты на выходных, то в понедельник используйте область подготовленных файлов для того, чтобы разделить проделанную работу по принципу минимум один коммит на задачу, давая полезные комментарии к каждому из них. Если несколько изменений касаются одного файла, используйте git add --patch для частичного добавления файлов в индекс (детально описано в разделе Интерактивное индексирование главы 7). Состояние проекта в конце ветки не зависит от количества сделанных вами коммитов, так как все изменения добавятся в один момент, поэтому постарайтесь облегчить задачу вашим коллегам, когда они будут просматривать ваши изменения. Такой подход так же облегчает извлечение или отмену отдельных изменений, если это вдруг потребуется в будущем. Раздел Перезапись истории главы 7 описывает ряд полезных трюков Git для переписывания истории изменений и интерактивного индексирования — используйте эти инструменты для создания чистой и понятной истории перед отправкой проделанной работы кому-то ещё. Последнее, что нужно иметь ввиду — это сообщение коммита. Привычка создавать качественные сообщения к коммитам позволяет упростить использование и взаимодействие посредством Git. Как правило, ваши сообщения должны начинаться кратким однострочным описанием не более 50 символов, затем должна идти пустая строка, после которой следует более детальное описание. Проект Git требует, чтобы детальное описание включало причину внесения изменений и сравнение с текущей реализацией — это хороший пример для подражания. Пишите сообщение коммита в императиве: «Fix bug» а не «Fixed bug» или «Fixes bug». Вот отличный шаблон хорошего сообщения коммита, который мы слегка адаптировали из шаблона, изначально написанного Тимом Поупом : Краткое (не более 50 символов) резюме с заглавной буквы Более детальный, поясняющий текст, если он требуется. Старайтесь не превышать длину строки в 72 символа. В некоторых случаях первая строка подразумевается как тема письма, а всё остальное -- как тело письма. Пустая строка, отделяющая сводку от тела, имеет решающее значение (за исключением случаев, когда детального описания нет); в противном случае такие инструменты, как rebase, могут вас запутать. Сообщения коммитов следует писать используя неопределённую форму глагола совершенного вида повелительного наклонения: «Fix bug» (Исправить баг), а не «Fixed bug» (Исправлен баг) или «Fixes bug» (Исправляет баг). Это соглашение соответствует сообщениям коммитов, генерируемых такими командами, как `git merge` и `git revert`. Последующие абзацы идут после пустых строк. - Допускаются обозначения пунктов списка - Обычно, элементы списка обозначаются с помощью тире или звёздочки, с одним пробелом перед ними, а разделяются пустой строкой, но соглашения могут отличаться - Допускается обратный абзацный отступ. Вам и вашим разработчикам будет гораздо проще, если все сообщения ваших коммитов будут так выглядеть. В проекте Git все сообщения к коммитам имеют расширенное форматирование — выполните команду git log --no-merges , чтобы увидеть как выглядит хорошо отформатированная история коммитов. Примечание Делайте как мы говорим, а не как делаем сами. Большинство примеров в этой книге не используют расширенного форматирования сообщений коммитов; вместо этого мы просто используем параметр -m для команды git commit . Поступайте так как мы говорим сейчас, а не так как делаем мы. Небольшая команда Самая простая ситуация, с которой вы можете столкнуться, это частный проект с одним или двумя другими разработчиками. «Частный» — в данном контексте понимается как проект с закрытым исходным кодом, недоступный для внешнего мира. Вы и другие разработчики имеете права записи в репозиторий. В такой среде вы можете использовать рабочий процесс, при котором выполняемые действия аналогичны использованию Subversion или другой централизованной системе. Вы всё ещё можете использовать преимущества создания коммитов оффлайн, значительно более простое ветвление и слияние, но процесс будет очень похожим; основное отличие в том, что слияние происходит на стороне клиента, а не на сервере во время коммита. Давайте посмотрим что происходит, когда два разработчика начинают работать вместе и используют общий репозиторий. Первый разработчик Джон клонирует репозиторий, вносит изменения и делает коммит локально. (В последующих примерах сообщения протокола заменены на … с целью их немного сократить.) # Компьютер Джона $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'Remove invalid default value' [master 738ee87] Remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) Второй разработчик Джессика делает то же самое — клонирует репозиторий и делает коммит: # Компьютер Джессики $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'Add reset task' [master fbff5bc] Add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Затем Джессика отправляет изменения на сервер: # Компьютер Джессики $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master В последней строке примера приведена полезная информация, выводимая после каждой операции отправки изменений. Её базовый формат такой <oldref>..<newref> fromref → toref , где oldref — коммит, на который указывала ветка до отправки, newref — новый коммит, на который ветка указывает сейчас, fromref — имя отправленной локальной ветки, toref — имя ветки в удалённом репозитории, в которую были отправлены изменения. Далее вы увидите похожие результаты в выводе команд, поэтому имея общее представление о значении поможет вам лучше понимать различные состояния репозиториев. Дополнительную информацию можно найти в документации к команде git-push . Возвращаясь к примеру, немного спустя, Джон вносит некоторые изменения, делает коммит и пытается отправить его на тот же сервер: # Компьютер Джона $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' В данном случае изменения Джона отклонены, так как Джессика уже отправила свои . Это особенно важно для понимания если вы привыкли к Subversion, потому что, как вы могли заметить, разработчики не редактировали один и тот же файл. Если Subversion автоматически делает слияние на сервере при условии, что редактировались разные файлы, то в Git вы должны сначала слить изменения локально. Джон должен получить изменения Джессики и слить их локально, прежде чем сможет отправить свои. Для начала, Джон получает изменения Джессики (слияния изменений пока что не происходит): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master В этот момент локальный репозиторий Джона выглядит примерно так: Рисунок 57. Расходящаяся история Джона Теперь Джон может слить полученные изменения Джессики со своей локальной веткой: $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Процесс слияния проходит гладко — история коммитов у Джона выглядит примерно так: Рисунок 58. Репозиторий Джона после слияния с origin/master Теперь Джон может протестировать новый код, чтобы убедиться в корректной работе объединённых изменений, после чего он может отправить объединённые изменения на сервер: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master В результате история коммитов у Джона выглядит так: Рисунок 59. История коммитов у Джона после отправки на origin сервер Тем временем Джессика создала тематическую ветку с названием issue54 и сделала в ней три коммита. Она ещё не получила изменения Джона, поэтому история коммитов у неё выглядит следующим образом: Рисунок 60. Тематическая ветка Джессики Внезапно Джессика узнаёт, что Джон отправил какие-то изменения на сервер и теперь она хочет на них взглянуть; для этого ей следует получить с сервера все новые изменения: # Компьютер Джессики $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master Это приводит к получению изменений, отправленных Джоном в репозиторий. Теперь, история коммитов у Джессики выглядит так: Рисунок 61. История коммитов Джессики после получения изменений Джона Джессика считает, что её тематическая ветка готова, но так же хочет знать какие изменения следует слить со своей работой перед отправкой на сервер. Для прояснения ситуации он выполняет команду git log : $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 Remove invalid default value issue54..origin/master — это синтаксис фильтра, который указывает Git отображать только список коммитов, которые существуют в последней ветке (в данном случае origin/master ), но отсутствуют в первой (в данном случае issue54 ). Более детально этот синтаксис рассматривается в разделе Диапазоны коммитов главы 7. В данном случае, в выводе команды мы видим только один коммит, сделанный Джоном и ещё не слитый Джессикой. Если она сольёт origin/master , то это будет единственный коммит, который изменит локальное состояние. Теперь, Джессика может слить изменения тематической ветки и изменения Джона ( origin/master ) в свою локальную ветку master , а затем отправить её на сервер. Для начала (при условии отсутствия изменений в тематической ветке, не включённых в коммит), Джессика переключается на свою ветку master : $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Обе ветки origin/master и issue54 являются отслеживаемыми, поэтому порядок слияния не важен. Конечный результат будет идентичным вне зависимости от порядка слияния, однако история коммитов будет немного отличаться. Джессика решает слить ветку issue54 первой: $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) Проблем не возникает; как можно заметить, это простое перемещение вперёд. Теперь Джессика заканчивает процесс локального слияния объединяя полученные ранее изменения Джона, находящиеся в ветке origin/master : $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Слияние прошло чисто и теперь история коммитов у Джессики выглядит следующим образом: Рисунок 62. История коммитов Джессики после слияния изменений Джона Теперь Джессика может отправить свою ветку master в origin/master , при условии что Джон больше не отправлял изменений: $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Каждый разработчик сделал коммиты несколько раз и успешно слил изменения другого. Рисунок 63. История коммитов Джессики после отправки на сервер Это один из самых простых рабочих процессов. В течение некоторого времени вы работаете в тематической ветке, а затем сливаете изменения в ветку master когда всё готово. Чтобы поделиться проделанной работой, вы сливаете её в вашу ветку master , затем получаете и сливаете изменения из ветки origin/master если таковые имеются, и наконец, отправляете все изменения в ветку master на сервере. В общем виде последовательность выглядит так: Рисунок 64. Общий вид последовательности событий в рабочем процессе для нескольких разработчиков Команда с руководителем В этом сценарии мы рассмотрим роли участников в более крупной частной команде. Вы узнаете как работать в окружении, где мелкие группы совместно работают над улучшениями, а затем их вклад интегрируется третьей стороной. Предположим, что Джон и Джессика вместе работают над одной функцией (назовём её «featureA»), при этом Джессика и Джози работают над другой («featureB»). В этом случае компания использует тип рабочего процесса с менеджером по интеграции, при котором работа отдельных групп интегрируется определёнными инженерами, а ветка master основного репозитория может быть обновлена только этими инженерами. При таком сценарии вся работа ведётся в отдельных ветках для каждой команды, а затем объединяется интегратором. Давайте рассмотрим рабочий процесс Джессики, так как она работает над двумя функциями, параллельно сотрудничая с разными разработчиками. Предположим, что репозиторий уже клонирован и она решает работать сначала над функцией featureA . Джессика создаёт новую ветку для этой функции и некоторое время работает над ней: # Компьютер Джессики $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'Add limit to log function' [featureA 3300904] Add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) В данный момент ей необходимо поделиться проделанной работой с Джоном, поэтому Джессика отправляет ветку featureA на сервер. У Джессики нет доступа на запись в ветку master (он есть только у интеграторов), поэтому для совместной работы с Джоном она отправляет изменения в другую ветку: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Джессика отправляет письмо Джону с уведомлением, что внесённые ей изменения уже доступны в ветке featureA . Пока Джессика ждёт ответа от Джона, она решает поработать над другой функцией featureB вместе с Джози. Для начала, Джесика создаёт новую тематическую ветку, базируясь на состоянии ветки master на сервере: # Компьютер Джессики $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' После этого, Джессика делает несколько коммитов в ветке featureB : $ vim lib/simplegit.rb $ git commit -am 'Make ls-tree function recursive' [featureB e5b0fdc] Make ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'Add ls-files' [featureB 8512791] Add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Репозиторий Джессики выглядит следующим образом: Рисунок 65. Начальное состояние истории коммитов Джессики Джессика готова отправить свою работу, но получает письмо Джози, что начальная работа уже отправлена на сервер в ветку featureBee . Теперь Джессике нужно слить эти изменения со своими перед отправкой на сервер. Изменения Джози она получает командой git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Полагая что Джессика находится в ветке featureB , она может слить полученные изменения Джози со своими при помощи команды git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) Одна небольшая проблема — ей нужно отправить слитые изменения из локальной ветки featureB в ветку featureBee на сервере. Для этого в команде git push Джессика указывает названия локальной и удалённой веток, разделённых двоеточием: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee Это называется спецификация ссылок . В разделе Спецификации ссылок главы 10 приведено более детальное описание спецификаций ссылок Git и различные способы их использования. Так же обратите внимание на флаг -u ; это сокращение для --set-upstream , который настраивает ветки для упрощения отправки и получения изменений в дальнейшем. После этого, Джессика получает письмо от Джона, в котором он сообщает, что отправил некоторые изменения в ветку featureA и просит их проверить. Джесика выполняет команду git fetch для получения всех новых изменений, включая изменения Джона: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Теперь, она может посмотреть что именно было изменено путём сравнения полученной ветки featureA со своей локальной веткой: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 Increase log output to 30 from 25 Если Джессику всё устраивает, то она сливает изменения Джона в свою ветку featureA : $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Джессика решает немного подправить, делает коммит в локальной ветке featureA и отправляет конечный результат на сервер: $ git commit -am 'Add small tweak to merged content' [featureA 774b3ed] Add small tweak to merged content 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA В результате история коммитов у Джессики выглядит так: Рисунок 66. История коммитов Джессики после изменений в тематической ветке Джессика, Джози и Джон информируют интеграторов, что ветки featureA и featureBee на сервере готовы к слиянию в основную. После того как интеграторы сольют эти ветки в основную, полученные изменения будут содержать коммит слияния, а история коммитов будет иметь вид: Рисунок 67. История коммитов Джессики после слияния тематических веток Многие переходят на Git именно из-за возможности параллельной работы нескольких команд в различных направлениях с последующим слиянием проделанной работы. Возможность совместной работы небольших подгрупп команды в удалённых ветках без необходимости вовлекать или мешать всей команде — огромное преимущество Git. Последовательность действий в описанном рабочем процессе выглядит следующим образом: Рисунок 68. Основная последовательность описанного рабочего процесса управляемой команды Форк публичного проекта Участие в публичном проекте сильно отличается. Так как у вас нет доступа обновлять ветки проекта напрямую, то передавать проделанную работу следует другим способом. В первом примере рассматривается участие в публичном проекте посредством форка на Git платформах, где возможно его простое создание. Большинство сайтов Git хостинга поддерживают такую функцию (включая GitHub, BitBucket, repo.or.cz и другие), как и большинство тех, кто сопровождает проекты, ожидают такого же стиля участия. Следующий раздел посвящён проектам, которые предпочитают принимать исправления в виде патчей по электронной почте. Для начала, вам следует клонировать основной репозиторий, создать тематическую ветку для одного или нескольких патчей и работать в ней. Обычно, последовательность действий выглядит так: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Примечание Возможно, вы захотите использовать rebase -i , чтобы объединить несколько коммитов в один или переставить их местами, чтобы сопровождающему было легче проверять патч — смотрите раздел Перезапись истории для получения детальной информации об интерактивном перебазировании. Когда работа в тематической ветке завершена и вы готовы передать изменения исходному проекту, перейдите на страницу исходного проекта и нажмите кнопку «Fork», тем самым создавая доступный для записи форк проекта. Затем нужно добавить URL на созданный проект как второй удалённый репозиторий, в нашем случае с именем myfork : $ git remote add myfork <url> После этого следует отправить проделанную работу в него. Проще отправить вашу тематическую ветку, в которой велась работа, чем сливать изменения в вашу ветку master и отправлять её. Если ваши изменения будут отклонены или какой-то из коммитов будет применён выборочно (команда cherry-pick более детально рассматривается в разделе Схема с перебазированием и отбором главы 5), то вы не сможете вернуть состояние вашей ветки master . Если менеджер проекта сольёт, перебазирует или выборочно применит ваши изменения, то вы сможете их получить из оригинального репозитория. В любом случае, отправить свои изменения вы можете командой: $ git push -u myfork featureA Когда ваши изменения отправлены в ваш форк, следует уведомить сопровождающих исходного проекта о том, что у вас есть изменения для интеграции. Обычно, это называется запросом слияния , который вы можете создать используя как веб сайт — GitHub использует собственный механизм запросов слияния, который будет рассмотрен в главе GitHub — так и команду git request-pull , отправив её вывод по почте. Команда git request-pull принимает в качестве аргументов название базовой ветки, в которую следует влить изменения из вашей тематической ветки, и ссылку на Git репозиторий, из которого следует получать изменения, а результатом будет список всех изменений, которые вы предлагаете внести. Например, если Джессика хочет отправить Джону запрос слияния и она отправила два коммита в тематическую ветку, то ей следует выполнить команду: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): Create new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): Add limit to log function Increase log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Вывод команды можно отправить сопровождающему проекта — в нём говорится с какого момента велась работа, приводится сводка коммитов и указывается откуда можно получить эти изменения. В проектах, где вы не являетесь сопровождающим, проще держать ветку master в соответствии с origin/master , а работать в тематических ветках — так вам будет проще отменить изменения, если они будут отклонены. Разделение направлений разработки по изолированным веткам облегчит их перебазирование, когда состояние основного репозитория изменится, а ваши коммиты уже не смогут быть чисто применены. Например, если вы собираетесь отправить исправления на другую тему, не продолжайте работать в той же тематической ветке — создайте новую, базируясь на ветке master основного репозитория: $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Теперь, каждая из ваших тематик разработки изолирована — аналогично очереди патчей — каждую из которых можно переписать, перебазировать или исправить без влияния на другие ветки: Рисунок 69. История коммитов в начале работы над featureB Предположим, что сопровождающий проекта слил некоторый набор других патчей, а затем пытается применить вашу первую ветку, но она уже не может быть слита без конфликтов. В этом случае вы можете попытаться перебазировать свою ветку относительно origin/master , разрешить конфликты и заново отправить свои изменения: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA Эти действия перепишут историю ваших коммитов, которая станет похожа на История коммитов после работы над featureA . Рисунок 70. История коммитов после работы над featureA Так как вы перебазировали ветку, то должны указать флаг -f во время отправки на сервер, чтобы переписать историю ветки featureA коммитами, не являющимися её потомками. Альтернативным решением может быть отправка этих исправлений в ветку с другим названием ( | 2026-01-13T09:29:44 |
https://git-scm.com/book/sl/v2/Porazdeljeni-Git-Prispevek-k-projektu | Git - Prispevek k projektu About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 5.2 Porazdeljeni Git - Prispevek k projektu Prispevek k projektu Glavna težava z opisovanjem, kako prispevati projektu, je, da obstaja veliko število spremenljivk, kako je to narejeno. Ker je Git zelo prilagodljiv, ljudje lahko in tudi res delajo skupaj na mnoge načine in problematično je opisovati, kako bi morali prispevati — vsak projekt je nekoliko drugačen. Nekatere vključene spremenljivke so število aktivnih ljudi, ki prispevajo, izbrani potek dela, vaš dostop potrjevanja in po možnosti zunanja metoda prispevkov. Prva spremenljivka je število aktivnih ljudi, ki prispevajo — koliko uporabnikov aktivno prispeva kodo temu projektu in kako pogosto? V mnogih primerih boste imeli dva ali tri razvijalce z nekaj potrditvami na dan ali po možnosti manj za projekte nekako v stanju mirovanja. Za večja podjetja ali projekte bi lahko število razvijalcev bilo v tisočih, s stotine ali tisoče potrditev, ki prihajajo vsak dan. To je pomembno, ker z več in več razvijalci naletite na večje težave, kako zagotavljati, da se vaša koda uporablja gladko oz. je enostavno združljiva. Spremembe, ki jih pošljete, lahko postanejo zastarele ali precej polomljene z delom, ki je bilo združeno, medtem ko ste delali, ali medtem ko vaše spremembe čakajo na odobritev ali uporabo. Kako lahko obdržite svojo kodo konsistentno posodobljeno in vaše potrditve veljavne? Naslednja spremenljivka je potek dela, ki je v uporabi za projekt. Je centraliziran, kjer ima vsak razvijalec enak dostop pisanja v glavno linijo kode? Ali ima projekt vzdrževalca ali integracijskega upravitelja, ki preveri vse popravke? So vsi popravki strokovno pregledani in odobreni? Ali ste vključeni v ta proces? Ali je sistem poročnika na mestu in ali jim morate najprej poslati svoje delo? Naslednja spremenljivka je vaš dostop potrditev. Potek dela, ki je zahtevan za prispevek k projektu, je veliko bolj drugačen, če imate dostop pisanja k projektu, kot če ga nimate. Če nimate dostopa za pisanje, kako ima projekt raje, da sprejme prispevano delo? Ali ima sploh pravilnik? Koliko dela prispevate na določen čas? Kako pogosto prispevate? Vsa ta vprašanja lahko vplivajo, kako efektivno prispevati projektu in katere poteke dela imate raje, oziroma so vam na voljo. Pokrili bomo vidike vsakega od teh v seriji primerov uporabe in se premaknili od enostavnega do bolj kompleksnega; morali bi biti sposobni skonstruirati določen potek dela, ki ga potrebujete v praksi iz teh primerov. Smernice potrjevanja Preden začnemo gledati določene primere uporabe, je tu hitro obvestilo o sporočilih potrditev. Imeti dobre smernice za ustvarjanje potrditev in se jih držati, naredi delo z Gitom in sodelovanjem z ostalimi veliko enostavnejše. Projekt Git ponuja dokument, ki začrta število dobrih nasvetov za ustvarjanje potrditev, iz katerih se pošljejo popravki — to lahko preberete v izvorni kodi Git v datoteki Documentation/SubmittingPatches . Kot prvo, ne želite poslati kakršnih koli napak praznih znakov. Git ponuja enostaven način, da to preverite — preden potrdite, poženite git diff --check , ki identificira vse možne napake praznih znakov in vam jih izpiše. Slika 56. Izpis git diff --check Če poženete ta ukaz preden potrdite, lahko poveste, ali ste tik pred tem, da potrdite tudi težave s praznimi znaki, ki lahko nagajajo ostalim razvijalcem. Naslednje poskusite narediti vsako potrditev kot logičen ločen skupek sprememb. Če lahko, poskusite narediti svoje spremembe prebavljive — ne kodirajte cel vikend na petih različnih težavah in nato pošljite vse kot eno masovno potrditev v ponedeljek. Tudi če ne naredite potrditve med koncem tedna, uporabite področje priprave v ponedeljek, da se loči vaše delo v vsaj eno potrditev na težavo z uporabnim sporočilom na potrditev. Če nekatere spremembe spremenijo isto datoteko, poskusite uporabiti git add --patch za delno pripravo datoteke (podrobno pokrito v razdelku Interaktivno pripravljanje ). Posnetek projekta pri vrhu veje je identičen, če naredite eno ali pa pet potrditev, dokler so vse spremembe dodane na neki točki, torej poskusite narediti stvari enostavne za svoje kolege razvijalce, ko bodo morali pregledati vaše spremembe. Ta pristop naredi enostavnejše tudi vlečenje ali povrnitev ene izmed skupka sprememb, če to kasneje potrebujete. Razdelek Prepisovanje zgodovine opisuje število uporabnih trikov Git za prepisovanje zgodovine in interaktivno dajanje datotek v področje priprave — uporabite ta orodja, da vam pomagajo izdelati čisto in razumljivo zgodovino, preden pošljete delo nekomu drugemu. Zadnja stvar za pomnjenje je sporočilo potrditve. Navaditi se ustvarjati kakovostna sporočila potrditev naredi uporabo in sodelovanje z Gitom veliko enostavnejše. Kot splošno pravilo bi se vaša sporočila morala začeti z eno vrstico, ki ni večja od 50 znakov in jedrnato opisuje skupek sprememb ter nato ji sledi prazna vrstica, ki ji sledi podrobnejša razlaga. Projekt Git zahteva, da bolj podrobna razlaga vključuje vašo motivacijo za spremembe in kontrast njene implementacije s prejšnjim obnašanjem — to je tudi dobra smernica za sledenje. Napišite svoja sporočila potrditev v velelniku: »Popravi hrošč« in ne »Popravljen hrošč« ali »To popravi hrošč«. Tu lahko sledite tej predlogi, ki smo jo malenkost prilagodili po tej, ki jo je prvotno napisal Tim Pope : Capitalized, short (50 chars or less) summary More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase will confuse you if you run the two together. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like git merge and git revert. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, followed by a single space, with blank lines in between, but conventions vary here - Use a hanging indent Če vsa vaša sporočila potrditev sledijo temu modelu, so stvari veliko enostavnejše za vas in razvijalce, s katerimi delate. Projekt Git ima dobro oblikovana sporočila potrditev — poskusite tam pognati git log --no-merges , da vidite, kakšna je lepo oblikovana zgodovina potrditev projekta. Opomba Naredite, kot pravimo, in ne kot to mi počnemo. Večina primerov v tej knjigi zaradi kratkosti nima lepo oblikovanih sporočil, kot je ta; namesto tega, uporabljamo možnost -m za git commit . Na kratko, naredite, kot pravimo, in ne kot to mi počnemo. Zasebna majhna ekipa Najenostavnejša nastavitev, na katero boste verjetno naleteli, je zasebni projekt z enim ali dvema razvijalcema. »Zasebni« v tem kontekstu pomeni zaprto kodo — ni dostopna za zunanji svet. Vi in ostali razvijalci imate vsi dostop potiskanja v repozitorij. V tem okolju lahko sledite poteku dela, ki je podoben, kakor ste morda delali, ko ste uporabljali Subversion ali drug centraliziran sistem. Še vedno dobite prednosti stvari, kot so potrjevanje brez povezave in prostrano enostavnejše razvejanje in združevanje, vendar potek dela je lahko zelo podoben; glavna razlika je, da se združevanje zgodi na strani odjemalca namesto na strežniku v času potrditve. Poglejmo, kako je lahko videti, ko dva razvijalca začneta delati skupaj z deljenim repozitorijem. Prvi razvijalec, John, klonira repozitorij, naredi spremembe in jih potrdi lokalno. Sporočila protokola so bila v teh primerih zamenjana s … , da se nekako skrajšajo. # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'Remove invalid default value' [master 738ee87] Remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) Druga razvijalka, Jessica, naredi isto stvar — klonira repozitorij in potrdi spremembo: # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'Add reset task' [master fbff5bc] Add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Sedaj Jessica potisne njeno delo na strežnik: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master Zadnja vrstica izhoda zgoraj prikazuje uporabno sporočilo o vrnitvi iz operacije potiska. Osnovni format je <oldref>..<newref> fromref → toref , kjer oldref pomeni staro referenco, newref pomeni novo referenco, fromref je ime lokalne reference, ki jo potiskamo, in toref je ime oddaljene reference, ki jo posodabljamo. Podoben izhod boste videli spodaj v razpravah, zato bo osnovna ideja o pomenu pomagala pri razumevanju različnih stanj repozitorijev. Več podrobnosti najdete v dokumentaciji za git-push . Če nadaljujemo s tem primerom, kmalu zatem John naredi nekaj sprememb, jih potrdi v svojem lokalnem repozitoriju in jih poskuša potisniti na isti strežnik: # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' V tem primeru Johnov potisk ni uspešen, ker je vmes potisnila Jessica njene spremembe. To je posebej pomembno razumeti, če ste vajeni Subversiona, ker boste opazili, da dva razvijalca nista uredila iste datoteke. Čeprav Subversion naredi to združevanje avtomatično na strežniku, če se urejajo različne datoteke, morate z Gitom najprej združiti potrditve lokalno. Z drugimi besedami, John mora najprej prenesti zgornje spremembe Jessice in jih združiti v svoj lokalni repozitorij, preden bo smel potisniti. Kot prvi korak John prenese delo Jessice (to samo prenese zgornje delo Jessice in ga še ne združi v Johnovo delo): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master Na tej točki je Johnov lokalni repozitorij videti nekako takole: Slika 57. Johnova drugačna zgodovina Sedaj lahko John združi Jessicino delo, ki ga je prenesel v svoje lokalno delo: $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Dokler gre to lokalno združevanje gladko, bo Johnova posodobljena zgodovina sedaj videti nekako takole: Slika 58. Johnov repozitorij po združitvi origin/master Sedaj lahko John testira to novo kodo, da zagotovi, da nobeno delo Jessice ne vpliva na nobeno njegovo in dokler poteka vse ustrezno, lahko potisne novo združeno delo na strežnik: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master Na koncu je Johnova zgodovina potrditev videti nekako takole: Slika 59. Johnova zgodovina po potisku na strežnik origin Vmes je Jessica ustvarila novo tematsko vejo imenovano issue54 in na tej veji naredila tri potrditve. Ni pa še prenesla Johnovih sprememb, zato je njena zgodovina potrditev videti nekako takole: Slika 60. Jessicina tematska veja Nenadoma Jessica izve, da je John potisnil nekaj novega dela na strežnik, in želi ga pogledati, torej lahko prenese vso novo vsebino iz strežnika, ki je še nima: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master To povleče delo, ki ga je vmes John potisnil. Zgodovina Jessice je sedaj videti takole: Slika 61. Zgodovina Jessice po prenosu Johnovih sprememb Jessica misli, da je njena tematska veja pripravljena, vendar želi vedeti, kateri del prenesenega Johnovega dela mora združiti v njeno delo, da lahko potisne. Požene git log , da ugotovi: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 Remove invalid default value Sintaksa issue54..origin/master je dnevniški filter, ki vpraša Git, da prikaže samo seznam potrditev, ki so na slednji veji (v tem primeru origin/master ) in ki niso na prvi veji (v tem primeru issue54 ). Skozi to sintakso bomo šli podrobneje v Obsegi potrditev . Iz zgornjega izpisa lahko vidimo, da je ena potrditev, ki jo je naredil John, in je Jessica ni združila v njeno lokalno delo. Če ona združi origin/master , je to ena potrditev, ki bo spremenila njeno lokalno delo. Sedaj lahko Jessica združi njeno tematsko delo v njeno vejo master , združi, Johnovo delo ( origin/master ) v njeno vejo master in nato potisne nazaj na strežnik. Najprej, (ko je potrdila vso delo na svoji tematski veji issue54 ), preklopi nazaj na njeno vejo master v pripravi, da integrira vso to delo: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jessica lahko najprej združi origin/master ali pa issue54 — obe sta iz povratnega toka, torej vrstni red ni pomemben. Zadnji posnetek bi moral biti identičen ne glede na vrstni red, ki ga izbere, samo zgodovina bo nekoliko drugačna. Najprej, izbere združiti vejo issue54 : $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) Ne pride do nobenih problemov; kot lahko vidite, je šlo za enostaven fast-forward. Sedaj Jessica zaključi proces lokalnega združevanja in združi prej preneseno delo Johna, ki čaka v veji origin/master : $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Vse se gladko združi in zgodovina Jessice je sedaj videti takole: Slika 62. Jessicina zgodovina po združitvi Johnovih sprememb Sedaj je origin/master dosegljiv iz Jessicine veje master , da lahko uspešno potisne (ob predpostavki, da John vmes ni ponovno potisnil še več sprememb): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Vsak razvijalec je naredil nekaj potrditev in uspešno združil delo drug drugega. Slika 63. Jessicina zgodovina po potisku vseh sprememb nazaj na strežnik To je eden najenostavnejših potekov dela. Nekaj časa delate, (v splošnem na tematski veji), in združite to delo v vašo vejo master , ko je pripravljeno za integracijo. Ko želite deliti to delo, prenesete in združite vašo vejo master iz origin/master , če se je kaj spremenilo, in na koncu potisnite na vejo master na strežniku. Splošno zaporedje je nekaj takega: Slika 64. Splošno zaporedje dogodkov za enostaven potek dela Git z več razvijalci Zasebne upravljane ekipe V tem naslednjem scenariju, boste pogledali vloge sodelavcev v večji zasebni skupini. Naučili se boste, kako delati v okolju, kjer sodelujejo manjše skupine na lastnostih, in nato so ti prispevki na osnovi ekip integrirani s strani druge stranke. Recimo, da John in Jessica delata skupaj na eni lastnosti (recimo featureA ), medtem ko Jessica in tretja razvijalka Josie delata na drugi (recimo featureB ). V tem primeru podjetje uporablja tip poteka dela upravitelja integracije, kjer je delo posameznih skupin integrirano samo od določenih inženirjev in veja master glavnega repozitorija je lahko posodobljena samo s strani teh inženirjev. V tem scenariju je vse delo narejeno na vejah na osnovi ekip in kasneje povlečene skupaj s strani povezovalcev. Sledimo poteku dela Jessice, kakor dela na dveh njenih lastnostih, vzporedno sodeluje z dvema različnima razvijalcema v tem okolju. Predpostavimo, da že ima svoj repozitorij kloniran in se odloči delati najprej na lastnosti featureA . Ustvari novo vejo za lastnost in naredi nekaj dela na njej: # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'Add limit to log function' [featureA 3300904] Add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) Na tej točki morate deliti nekaj dela z Johnom, torej potisne njene potrditve veje featureA na strežnik. Jessica nima dostopa potiskanja na vejo master — to imajo samo povezovalci — torej mora potisniti na drugo vejo, da lahko sodeluje z Johnom: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica sporoči Johnu po e-pošti, da je potisnila nekaj dela v vejo imenovano featureA , in on lahko to sedaj pogleda. Medtem ko čaka na povratne informacije od Johna, se Jessica odloči začeti delati na lastnosti featureB z Josie. Da začne, ustvari novo vejo lastnosti, ki je osnovana na strežniški veji master : # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Sedaj, Jessica naredi nekaj potrditev na veji featureB : $ vim lib/simplegit.rb $ git commit -am 'Make ls-tree function recursive' [featureB e5b0fdc] Make ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'Add ls-files' [featureB 8512791] Add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Jessicin repozitorij je videti sedaj takole: Slika 65. Jessicina prvotna zgodovina potrditev Pripravljena je potisniti njeno delo, vendar dobi e-pošto od Josie, da je veja featureB z nekaj začetnega dela na njej že potisnjena na strežnik kot featureBee . Jessica mora najprej združiti te spremembe v njeno lastno, preden lahko potisne svoje delo na strežnik. Jessica najprej prenese spremembe Josie z git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Ob predpostavki, da je Jessica še vedno na svoji izvlečeni veji featureB , lahko sedaj združi delo Josie v to vejo z git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) V tem trenutku Jessica želi vse združeno delo featureB potisniti nazaj na strežnik, vendar noče preprosto potisniti svoje veje featureB . Ker je Josie že začela z zgornjo vejo featureBee , želi Jessica potisniti na to vejo, kar stori s: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee To se imenuje refspec . Glejte razdelek Refspec za bolj podrobno diskusijo refspec Gita in različnih stvari, ki jih lahko naredite z njimi. Bodite pozorni tudi na zastavico -u ; to je okrajšava za --set-upstream , ki nastavi veje za enostavnejše kasnejše potiskanje in vlečenje. Nenadoma Jessica prejme e-pošto od Johna, ki ji sporoči, da je potisnil nekaj sprememb na vejo featureA , na kateri sodelujeta, in jo prosi, naj si jih ogleda. Jessica ponovno zažene preprost ukaz git fetch , da prenese vse nove vsebine s strežnika, vključno (seveda) z Johnovim najnovejšim delom: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessica lahko prikaže dnevnik Johnovega novega dela s primerjavo vsebine na novo prenesene veje featureA s svojo lokalno kopijo iste veje: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 Increase log output to 30 from 25 Če je Jessici všeč, kar vidi, lahko združi novo delo Johna v njeno lokalno vejo featureA : $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Nazadnje bi Jessica lahko želela narediti nekaj manjših sprememb na vsem tem združenem delu, zato je prosta, da naredi te spremembe, jih potrdi v svoji lokalni veji featureA in potisne končni rezultat nazaj na strežnik: $ git commit -am 'Add small tweak to merged content' [featureA 774b3ed] Add small tweak to merged content 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Zgodovina potrditev Jessice je sedaj videti nekako takole: Slika 66. Jessicina zgodovina po potrditvi na veji lastnosti V nekem trenutku Jessica, Josie in John obvestijo povezovalce, da sta veji featureA in featureBee na strežniku pripravljeni za integracijo v glavno vejo. Ko povezovalci združijo ti veji v glavno vejo, bo prenos prinesel novo potrditev združitve, zaradi česar bo zgodovina videti takole: Slika 67. Jessicina zgodovina po združitvi obeh njenih tematskih vej Zaradi te zmožnosti mnoge skupine preklopijo na Git, da imajo več ekip, ki delajo vzporedno in združujejo na različnih vrsticah dela kasneje v procesu. Zmožnost manjših podskupin ekipe, da sodelujejo preko oddaljenih vej brez potrebe po vključevanju ali oviri celotne ekipe, je velika prednost Gita. Zaporedje poteka dela, ki ste ga tu videli, je nekaj takega: Slika 68. Osnovno zaporedje tega poteka dela upravljane ekipe Razvejan javni projekt Prispevki k javnim projektom so nekoliko drugačni. Ker nimate dovoljenja neposredno posodobiti veje na projektu, morate nekako dati delo vzdrževalcem na drug način. Prvi primer opisuje prispevke preko razvejanja na gostiteljih Git, ki podpirajo enostavno razvejanje. Mnoge strani gostiteljev to podpirajo (vključno z GitHub, BitBucket, Google Code, repo.or.cz in ostalimi) in mnogi vzdrževalci projektov pričakujejo ta stil prispevkov. Naslednji razdelek se ukvarja s projekti, ki imajo raje sprejeti prispevke popravkov preko e-pošte. Najprej boste verjetno želeli klonirati glavni repozitorij, ustvariti tematsko vejo za programski popravek ali serijo popravkov, ki jih planirate prispevati in narediti delo tam. Zaporedje je videti v osnovi takole: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Opomba Lahko boste želeli uporabiti rebase -i , da svoje delo stisnete v eno potrditev ali delo preuredite v potrditve, da naredite programski popravek enostavnejši za pregled razvijalcev — za več informacij o interaktivnem ponovnem baziranju glejte razdelek Prepisovanje zgodovine . Ko je delo vaše veje končano in ste pripravljeni prispevati nazaj vzdrževalcem, pojdite na prvotno stran projekta in kliknite na gumb »Fork«, kar bo ustvarilo vašo lastno zapisljivo razvejitev projekta. Nato morate dodati ta novi URL repozitorija kot novo daljavo svojega lokalnega repozitorija; v tem primeru ga imenujmo myfork : $ git remote add myfork <url> Nato morate potisniti svoje novo delo v ta repozitorij. Najenostavnejše je potisniti tematsko vejo, na kateri delate, na vaš razvejan repozitorij namesto združevanja v vašo vejo master in potiskanja tega navzgor. Razlog je, da če delo ni sprejeto, ali so izbrane samo najboljše spremembe (angl. cherry picking ), vam ni treba previti nazaj vaše veje master (operacija Gita cherry-pick je pokrita bolj podrobno v Poteki dela ponovnega baziranja in izbire najboljšega ). Če vzdrževalci združijo, ponovno bazirajo ali izberejo samo najboljše spremembe vašega dela, ga boste tako ali tako eventualno povlekli nazaj iz njihovega repozitorija: V kateremkoli primeru lahko potisnete svoje delo na naslednji način: $ git push -u myfork featureA Ko je bilo vaše delo potisnjeno na vašo razvejitev, morate obvestiti vzdrževalce prvotnega projekta, da imate delo, ki ga želite, da ga združijo. To je pogostokrat imenovano zahtevek potega in tak zahtevek običajno generirate preko spletne strani — GitHub ima svoj lastni mehanizem zahtevkov potega, ki jih bomo obravnavali v GitHub — ali pa poženete ukaz git request-pull in pošljete vzdrževalcu projekta dani izpis ročno po e-pošti. Ukaz git request-pull vzame osnovno vejo, v katero želite povleči svojo tematsko vejo, in URL repozitorija Git, iz katerega želite, da ga povlečejo, ter izpiše povzetek vseh sprememb, za katere želite, da se povlečejo. Na primer, če Jessica želi poslati Johnu zahtevek potega in je končala dve potrditvi na tematski veji, ki jo je ravnokar potisnila, lahko požene tole: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): Create new function are available in the git repository at: https://githost/simplegit.git featureA Jessica Smith (2): Add limit to log function Increase log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Ta izpis se lahko pošlje vzdrževalcu — pove jim, od kod je delo razvejano, povzame potrditve in pove, od kod povleči to delo. Na projektu, za katerega niste vzdrževalec, je v splošnem enostavnejše imeti vejo, kot je master , ki vedno sledi origin/master , in narediti vaše delo v tematskih vejah, ki jih lahko enostavno zavržete, če so zavrnjene. Delovne teme, izolirane v tematske veje, so vam tudi enostavnejše, da ponovno bazirate vaše delo, če se je konica glavnega repozitorija vmes premaknila in vaših potrditev ni več mogoče gladko uporabiti. Na primer, če želite poslati drugo temo dela projekta, ne nadaljujte delo na tematski veji, ki ste jo ravnokar potisnili, začnite raje znova iz veje master glavnega repozitorija: $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Sedaj je vsaka od vaših tem vsebovana znotraj silosa — podobno kot čakalna vrsta popravka — ki jo lahko prepišete in spremenite, brez da se teme med seboj vmešavajo ali so soodvisne druga od druge: Slika 69. Začetna zgodovina potrjevanja dela featureB Recimo, da je vzdrževalec projekta povlekel veliko ostalih popravkov in poskusil vašo prvo vejo, vendar se ne združuje več gladko. V tem primeru lahko to vejo poskusite ponovno bazirati na vrh origin/master , rešite konflikte za vzdrževalca in nato ponovno pošljete svoje spremembe: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA To prepiše vašo zgodovino, da je sedaj videti kot na sliki Zgodovina potrditev po delu featureA . Slika 70. Zgodovina potrditev po delu featureA Ker ste vejo ponovno bazirali, morate določiti -f za vaš ukaz potiskanja, da lahko zamenjate vejo featureA na strežniku s potrditvijo, ki ni njen potomec. Alternativa bi bila potisniti to novo delo na drugo vejo na strežniku (mogoče imenovano featureAv2 ). Poglejmo en bolj verjeten scenarij: vzdrževalec je pogledal delo v vaši drugi veji in mu je zasnova všeč, vendar bi rad, da spremenite podrobnost implementacije. To priložnost boste tudi vzeli, da premaknete delo, da bo osnovano na trenutni veji projekta master . Začnete novo vejo, ki je osnovana na trenutni veji origin/master , tam stisnite spremembe featureB , rešite kakršnekoli konflikte, naredite implementacijo sprememb in nato to potisnite kot novo vejo: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 Možnost --squash vzame vso delo na združeni veji in jih stisne v en skupek sprememb, ki ustvari stanje repozitorija, kakor da bi se zgodilo resnično združevanje, ne da dejansko naredi potrditev združitve. To pomeni, da bo vaša prihodnja potrditev imela samo eno nadrejeno in vam omogoča uvedbo vseh sprememb iz druge veje ter nato naredite več sprememb pred snemanjem nove potrditve. Uporabna je lahko tudi možnost --no-commit , ki zakasni potrditev združitve v primeru privzetega procesa združevanja. Sedaj lahko pošljete vzdrževalcu sporočilo, da ste naredili zahtevane spremembe in da te spremembe lahko najdejo v vaši veji featureBv2 . Slika 71. Zgodovina potrditev po delu featureBv2 Javni projekt preko e-pošte Mnogi projekti imajo ustaljene postopke za sprejemanje popravkov — preveriti boste morali določena pravila za vsak projekt, ker se razlikujejo. Odkar je na voljo nekaj starejših, večjih projektov, ki sprejemajo popravke preko razvijalskega e-poštnega seznama, bomo šli sedaj skozi primer tega. Potek dela je podoben prejšnjemu primeru uporabe — ustvarite tematske veje za vsake serije popravka, na katerih delate. Razlika je, kako jih pošljete projektu. Namesto razvejanja projekta in potiskanja v svojo lastno zapisljivo različico generirate e-poštno različico za vsako od serij potrditev in jih pošljete po e-pošti razvijalskemu e-poštnemu seznamu: $ git checkout -b topicA ... work ... $ git commit ... work ... $ git commit Sedaj imate dve potrditvi, ki ju želite poslati na e-poštni seznam. Uporabili boste git format-patch , da generirate mbox oblikovane datoteke, ki jih lahko pošljete preko e-pošte na seznam — vsako potrditev pretvori v sporočilo e-pošte s prvo vrstico sporočila potrditve kot zadevo in preostanek sporočila ter programski popravek, ki ga potrditev predstavlja kot telo. Dobra stvar pri tem je, da uporaba popravka generiranega iz e-pošte s format-patch ustrezno ohrani vse informacije potrditve. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch Ukaz format-patch izpiše imena datotek popravka, ki ga ustvari. Preklop -M pove Gitu, da išče preimenovanja. Datoteke so na koncu videti takole: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] Add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 Lahko tudi uredite te datoteke popravka, da dodate več informacij za seznam e-pošte, za katere ne želite, da se prikažejo v sporočilu potrditve. Če dodate besedilo med vrstico --- in začetek popravka (vrstica diff --git ), potem ga razvijalci lahko preberejo, vendar proces popravka vsebino izključuje. Da to pošljete po e-pošti na e-poštni seznam, lahko prilepite datoteko v vaš e-poštni program, ali pa pošljete preko programa ukazne vrstice. Lepljenje teksta pogostokrat povzroča težave oblikovanja, posebej s »pametnejšimi« odjemalci, ki ne ohranjajo ustrezno novih vrstic in ostalih praznih znakov. Na srečo, Git ponuja orodje, ki vam pomaga poslati ustrezno oblikovane popravke preko IMAP, kar je za vas lahko enostavnejše. Prikazali bomo, kako poslati programski popravek preko Gmaila, kar je e-poštni agent, ki ga najbolje poznamo; preberete lahko podrobna navodila za število poštnih programov na koncu zgoraj omenjene datoteke Documentation/SubmittingPatches v izvorni kodi Git. Najprej morate nastaviti razdelek imap v vaši datoteki ~/.gitconfig . Nastavite lahko vsako vrednost ločeno s serijo ukazov git config ali pa jih dodate ročno, vendar na koncu bi vaša nastavitvena datoteka morala biti videti nekako takole: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false Če vaš strežnik IMAP ne uporablja SSL, zadnji dve vrstici verjetno nista potrebni in vrednost gostitelja bo imap:// namesto imaps:// . Ko je to nastavljeno, lahko uporabite git imap-send , da dodate serijo popravkov v mapo Drafts določenega strežnika IMAP: $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done V tem trenutku bi morali imeti dostop do vaše mape osnutkov (angl. Drafts ), lahko spremenite polje »To« na seznam e-pošte, na katerega pošiljate programski popravek, opcijsko »CC« za vzdrževalca ali osebo, odgovorno za ta razdelek, in lahko ga pošljete. Programski popravek lahko pošljete tudi preko strežnika SMTP. Kot prej, lahko nastavite vsako vrednost ločeno s serijo ukazov git config , ali pa jih dodate ročno v razdelek sendemail vaše datoteke ~/.gitconfig : [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 Ko je to narejeno, lahko uporabite git send-email , da pošljete svoje popravke: $ git send-email *.patch 0001-add-limit-to-log-function.patch 0002-increase-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Nato Git izpljune kopico informacij dnevnika, kar je videti nekako takole za vsak programski popravek, ki ga pošiljate: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] Add limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Namig Za pomoč, kako nastaviti vaš sistem in e-pošto, več nasvetov in trikov ter peskovnik za pošiljanje preizkusnega popravka preko e-pošte, obiščite git-send-email.io . Povzetek V tem razdelku smo obravnavali več potekov dela in razpravljali o razlikah med delom v majhni ekipi na zaprtem projektu in prispevku k velikemu javnemu projektu. Sedaj veste, kako pred potrditvijo preveriti napake praznih znakov in napisati znate odlično sporočilo potrditve. Naučili ste se, kako oblikovati popravke in kako jih pošljete po e-pošti na seznam razvijalcev. Razpravljali smo tudi o združevanju pri različnih potekih dela. Zdaj ste dobro pripravljeni za sodelovanje na katerem koli projektu. V nadaljevanju boste videli, kako deluje druga plat medalje: vzdrževanje projekta Git. Naučili se boste, kako biti dobronamerni diktator ali integracijski upravitelj. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/id/v2/Git-Branching-Branching-Workflows | Git - Branching Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.4 Git Branching - Branching Workflows Branching Workflows Now that you have the basics of branching and merging down, what can or should you do with them? In this section, we’ll cover some common workflows that this lightweight branching makes possible, so you can decide if you would like to incorporate it into your own development cycle. Long-Running Branches Because Git uses a simple three-way merge, merging from one branch into another multiple times over a long period is generally easy to do. This means you can have several branches that are always open and that you use for different stages of your development cycle; you can merge regularly from some of them into others. Many Git developers have a workflow that embraces this approach, such as having only code that is entirely stable in their master branch – possibly only code that has been or will be released. They have another parallel branch named develop or next that they work from or use to test stability – it isn’t necessarily always stable, but whenever it gets to a stable state, it can be merged into master . It’s used to pull in topic branches (short-lived branches, like your earlier iss53 branch) when they’re ready, to make sure they pass all the tests and don’t introduce bugs. In reality, we’re talking about pointers moving up the line of commits you’re making. The stable branches are farther down the line in your commit history, and the bleeding-edge branches are farther up the history. Figure 26. A linear view of progressive-stability branching It’s generally easier to think about them as work silos, where sets of commits graduate to a more stable silo when they’re fully tested. Figure 27. A “silo” view of progressive-stability branching You can keep doing this for several levels of stability. Some larger projects also have a proposed or pu (proposed updates) branch that has integrated branches that may not be ready to go into the next or master branch. The idea is that your branches are at various levels of stability; when they reach a more stable level, they’re merged into the branch above them. Again, having multiple long-running branches isn’t necessary, but it’s often helpful, especially when you’re dealing with very large or complex projects. Topic Branches Topic branches, however, are useful in projects of any size. A topic branch is a short-lived branch that you create and use for a single particular feature or related work. This is something you’ve likely never done with a VCS before because it’s generally too expensive to create and merge branches. But in Git it’s common to create, work on, merge, and delete branches several times a day. You saw this in the last section with the iss53 and hotfix branches you created. You did a few commits on them and deleted them directly after merging them into your main branch. This technique allows you to context-switch quickly and completely – because your work is separated into silos where all the changes in that branch have to do with that topic, it’s easier to see what has happened during code review and such. You can keep the changes there for minutes, days, or months, and merge them in when they’re ready, regardless of the order in which they were created or worked on. Consider an example of doing some work (on master ), branching off for an issue ( iss91 ), working on it for a bit, branching off the second branch to try another way of handling the same thing ( iss91v2 ), going back to your master branch and working there for a while, and then branching off there to do some work that you’re not sure is a good idea ( dumbidea branch). Your commit history will look something like this: Figure 28. Multiple topic branches Now, let’s say you decide you like the second solution to your issue best ( iss91v2 ); and you showed the dumbidea branch to your coworkers, and it turns out to be genius. You can throw away the original iss91 branch (losing commits C5 and C6 ) and merge in the other two. Your history then looks like this: Figure 29. History after merging dumbidea and iss91v2 We will go into more detail about the various possible workflows for your Git project in Distributed Git , so before you decide which branching scheme your next project will use, be sure to read that chapter. It’s important to remember when you’re doing all this that these branches are completely local. When you’re branching and merging, everything is being done only in your Git repository – no server communication is happening. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://www.atlassian.com/ko/software/jira/service-management/retail-ecommerce | 소매업체 및 전자 상거래 회사를 위한 Jira Service Management | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 솔루션 사용 사례별 기능별 업계별 사용 사례별 IT 지원 IT 운영 비즈니스 팀 고객 서비스 인사 기능별 소규모 팀 Premium Enterprise 업계별 기술 및 통신 금융 서비스 리테일 제조 Back 가격 리소스 유형별 ITSM 제품 가이드 템플릿 추가 리소스 Back 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Jira Service Management로 소매 및 전자 상거래 지원 강화 소매업체 및 전자 상거래 회사는 지원 만족도를 높이고 효율적으로 확장하고 고객의 데이터를 보호하는 AI 기반 경험으로 경쟁에서 앞서나가기 위해 Jira Service Management를 사용합니다. 무료 평가판 사용 데모 참여 소매 서비스 최신화 소매 채널 전반의 고객 피드백을 통합하여 프로세스와 워크플로를 간소화하는 사용자 지정 가능한 AI 기반의 단일 플랫폼으로 팀을 통합하세요. 직원이 모든 운영 채널에서 인벤토리, 판매 및 고객 행동에 대한 실시간 데이터에 액세스할 수 있도록 지원하세요. 자세히 알아보기 고객 만족도 증가 소매 운영 팀은 하나의 플랫폼에서 공동 작업하여 이슈를 더 빠르게 해결하고 고객 만족도 점수를 높일 수 있습니다. 팀은 AI를 사용하여 고객 감정을 측정하고 요청 , 인시던트 , 변경 사항 에 신속하게 대응할 수 있습니다. 전자 상거래를 효율적으로 확장 시장의 경쟁이 치열해짐에 따라 속도와 서비스가 아주 중요해졌습니다. AI 기반 구성 및 코드가 필요하지 않은 양식, 워크플로, 자동화를 사용하여 고객에게 효율적인 온라인 소매 서비스를 제공하세요. 자세히 알아보기 고객 데이터 보호 중요한 고객 정보와 데이터를 다루는 업계에 해당하는 소매업체 및 전자 상거래 회사에서는 기술을 최신 상태로 유지하고 개인 정보 보호를 보장하고 컴플라이언스를 유지하는 것이 매우 중요합니다. Atlassian 보안 소매업체 및 전자 상거래 회사를 위한 Jira Service Management 기능 모든 기능 살펴보기 요청 관리 옴니채널, AI 기반 Virtual Service Agent 지원을 통해 고객에게 도움이 필요한 장소 및 시간에 신속하게 도움을 제공할 수 있습니다. 자산 관리 인벤토리를 효율적으로 관리하고 소유권 및 수명 주기를 추적하고 비용을 줄이세요. 자동화된 워크플로 AI를 사용하여 관련 Jira 티켓 연결 또는 이슈 자동 할당과 같이 워크플로를 간소화하는 자동화를 빠르게 구축하세요. 구성 관리 중요한 애플리케이션 및 서비스를 지원하는 인프라에 대한 가시성을 확보하세요. 위험을 최소화할 수 있도록 서비스 종속성을 파악합니다. SLA에 따라 실행 우선 순위가 지정된 큐를 사용하여 중요한 고객 요구 사항을 먼저 완료하세요. AI를 사용하여 요청을 빠르게 분류하고 응답하고 해결하세요. 인시던트에 빠르게 대응 개발, 지원, 운영 팀을 하나로 모으고 AIOps 기능을 사용하여 인시던트에 신속하게 대응하고 해결하고 인시던트에서 배우세요. 서비스 관리에 대한 Atlassian의 접근 방식에 대해 자세히 알아보세요 가이드 읽기 템플릿 빠르게 시작하는 데 도움이 되는 고객 서비스 및 ITSM 템플릿 조치를 취하는 데 필요한 컨텍스트를 적절한 담당자에게 제공하세요. 요청, 인시던트, 변경 사항을 관리하여 뛰어난 서비스를 빠르게 제공하세요. AI 기반 프로젝트 구성을 사용하여 사용자 지정 요청 유형, 양식 필드, 자동화를 만들 수도 있습니다. 템플릿 살펴보기 Virtual Service Agent 지원 상시 가동되는 AI 기반 지원 AI의 도움을 받아 지원 상호 작용을 처리하는 Virtual Service Agent로 옴니채널 서비스를 강화하세요. 사용자 지정 대화 흐름을 만들어 비밀번호 재설정과 같은 작업을 자동화하거나 기존 참조 자료를 활용하여 일반적인 요청에 대한 응답을 생성하세요. 고객에게 도움이 필요한 장소 및 시간에 도움을 제공하면서 에이전트의 시간을 절약하세요. 자세히 알아보기 50,000개 이상의 회사에서 Jira Service Management를 사용합니다 “사용한 이후로 평균 4.9/5점의 만족도 점수를 받았으며 정말 놀라웠습니다. 이전 솔루션을 사용할 때는 불만밖에 받지 못했습니다." Rob Crompton, The Very Group 서비스 관리 책임자 “저희는 Jira Service Management를 사용하면서 더 애자일해졌습니다. 효율적인 올인원 솔루션을 통해 무슨 일이 일어나는지 확인하고 모두가 따라야 할 방향을 파악하고 그 덕분에 훨씬 더 효과적으로 실행할 수 있기 때문입니다.” 어시스턴트 부사장, Atlassian 소매 고객 ← → 많은 조직에서 수상 경력의 소프트웨어를 신뢰하는 이유를 알아보세요 Atlassian은 2022년 Gartner® Magic Quadrant™에서 IT 서비스 관리 플랫폼 부문 리더로 선정되었습니다. Atlassian Jira Service Management의 Total Economic Impact™ 에 대해 알아보세요. Gartner Peer Insights 에서 Jira Service Management가 받은 점수를 확인하세요. AI 기반 소매 및 전자 상거래 서비스 관리 뛰어난 서비스 경험을 제공하고 작업 흐름을 가속화하려면 Jira Service Management를 선택하세요. 무료 평가판 사용 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:44 |
https://git-scm.com/book/zh-tw/v2/%e9%96%8b%e5%a7%8b-Git-%e5%ae%89%e8%a3%9d%e6%95%99%e5%ad%b8 | Git - Git 安裝教學 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.5 開始 - Git 安裝教學 Git 安裝教學 在你開始使用 Git 以前，你必須先在你的電腦設定到讓 Git 可以使用。 如果你之前已經安裝過，那麼你應該確認 Git 已經升級到最新版。 你可以使用套件（package）進行安裝、透過安裝程式或是自行下載原始碼自己編譯。 筆記 本書在撰寫時，Git 的版本為 2.0.0 。 雖然本書使用到的指令在比較舊版的 Git 中通常都可以使用，但是仍然會有一些指令的行為相差極大或是根本無法使用。 Git 提供了相當出色的向下相容性，所以如果你目前的 Git 版本大於 2.0，那麼應該是不會有什麼太大的問題。 在 Linux 安裝 如果你想要透過二進位安裝程式安裝基本的 Git 工具集，你通常可以直接透過你所用的發行版（distribution）內建的基礎套件管理工具。 舉例來說，如果你使用的是 Fedora，你可以使用 yum： $ sudo yum install git-all 如果你是使用 Debian 系列的發行版，如 Ubuntu，你可以使用 apt-get： $ sudo apt-get install git-all 如果需要更多選擇，Git 官方網站上有更多其他的發行版中安裝 Git 的安裝步驟，網址為 http://git-scm.com/download/linux 。 在 Mac 中安裝 在 Mac 中安裝 Git 有很多種方法。 最簡單的方法應該就是直接安裝 Xcode 命令列開發者工具（Xcode Command Line Tools）。 在 Mavericks (10.9) 或更新版的系統中，你甚至可以直接在終端機中直接打入「git」指令。 如果系統發現你還沒安裝過，便會自動提示你進行安裝。 如果你希望安裝更新的版本，你也可以透過二進位安裝程式安裝。 在 Git 官方網站上有維護最新版的安裝程式可供下載，網址在 http://git-scm.com/download/mac 。 圖表 7. Git OS X 安裝程式 你還可以透過 GitHub 的 Mac 安裝程式來安裝。 GitHub 的 Git 圖形化工具有提供相對應的選項讓你安裝 Git 命令列工具。 你可以從 GitHub for Mac 官方網站下載，網址在 http://mac.github.com 。 在 Windows 中安裝 在 Windows 中安裝 Git 也有很多種方式。 最正式的安裝程式在 Git 官方網站可供下載。 你只需要連到 http://git-scm.com/download/win 然後下載就會自動開始。 請注意這是一個名為 Git for Windows 的專案，與 Git 本身是互相獨立的。如果你需要更多資料，請查閱 http://git-for-windows.github.io/ 。 另一個安裝 Git 的簡單方法就是直接安裝 GitHub for Window。 這個安裝程式內已經預設提供 Git 的命令列版本和圖形化工具。 而且它也能夠完美搭配 Powershell，設定實體憑證快取和完整的 CRLF 設定。 我們將會在本書的其他章節學到這些事情，但我只想強調，這就是你需要的東西。 你可以直接從 GitHub for Windows 下載，網址在 http://windows.github.com 。 從原始碼安裝 某些人可能會發現從原始碼安裝 Git 反而比較好用，因為你可以拿到最新的 Git 版本。 通常二進位安裝程式都會落後於 Git 原始碼的版本，雖然 Git 近幾年已經逐漸成熟，兩者的版本差異可能不大。 如果你希望從原始碼安裝 Git，你需要擁有以下 Git 所需的函式庫：curl, zlib, openssl, expat 和 libiconv。 舉例來說，如果你的系統有 yum（例如 Fedora）或 apt-get（例如 Debian 系列的發行版），你可以使用其中一個指令來安裝這些最小相依關係（the minimal dependencies），這樣才有辦法安裝編譯並安裝 Git 可執行檔。 $ sudo yum install curl-devel expat-devel gettext-devel \ openssl-devel perl-devel zlib-devel $ sudo apt-get install libcurl4-gnutls-dev libexpat1-dev gettext \ libz-dev libssl-dev 為了能夠建立這些格式（doc、html、info）的文件，你還需要安裝這些額外的相依關係（注意：RHEL 系列（像是 CentOS、Scientific Linux）的使用者必需 啟用 EPEL 版本庫 ，才能下載 docbook2X 套件）： $ sudo yum install asciidoc xmlto docbook2X $ sudo apt-get install asciidoc xmlto docbook2x 另外，如果你使用 Fedora 或 RHEL 系列，你還需要做這個： $ sudo ln -s /usr/bin/db2x_docbook2texi /usr/bin/docbook2x-texi 這是因為所使用的檔名不同。（譯注: 此行命令是對 docbook2x-texi 做一個捷徑，將其「連結」到實際上所使用的 db2x_docbook2texi。） 當你成功的安裝所有必備的相依關係，你就可以繼續下一步：從以下其中一個地方抓回最新的 Git 原始碼 tarball 壓縮檔。 你可以從 Kernel.org 網站取得，網址在 https://www.kernel.org/pub/software/scm/git ；或是在 GitHub 上面的鏡像，網址在 https://github.com/git/git/releases 。 通常在 GitHub 網站上你會比較容易知道哪個原始碼是最新的；但是在 kernel.org 網站上會同時提供該檔案的數位簽章，以便你下載後對檔案進行驗證。 再來，編譯並安裝 Git： $ tar -zxf git-2.0.0.tar.gz $ cd git-2.0.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc install-html install-info 當你安裝完以後，你就可以透過 Git 來取得 Git 最新的原始碼如下： $ git clone git://git.kernel.org/pub/scm/git/git.git prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
https://git-scm.com/book/id/v2/Distributed-Git-Contributing-to-a-Project | Git - Contributing to a Project About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Distributed Git - Contributing to a Project Contributing to a Project The main difficulty with describing how to contribute to a project is that there are a huge number of variations on how it’s done. Because Git is very flexible, people can and do work together in many ways, and it’s problematic to describe how you should contribute – every project is a bit different. Some of the variables involved are active contributor count, chosen workflow, your commit access, and possibly the external contribution method. The first variable is active contributor count – how many users are actively contributing code to this project, and how often? In many instances, you’ll have two or three developers with a few commits a day, or possibly less for somewhat dormant projects. For larger companies or projects, the number of developers could be in the thousands, with hundreds or thousands of commits coming in each day. This is important because with more and more developers, you run into more issues with making sure your code applies cleanly or can be easily merged. Changes you submit may be rendered obsolete or severely broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next variable is the workflow in use for the project. Is it centralized, with each developer having equal write access to the main codeline? Does the project have a maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your work to them first? The next issue is your commit access. The workflow required in order to contribute to a project is much different if you have write access to the project than if you don’t. If you don’t have write access, how does the project prefer to accept contributed work? Does it even have a policy? How much work are you contributing at a time? How often do you contribute? All these questions can affect how you contribute effectively to a project and what workflows are preferred or available to you. We’ll cover aspects of each of these in a series of use cases, moving from simple to more complex; you should be able to construct the specific workflows you need in practice from these examples. Commit Guidelines Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches – you can read it in the Git source code in the Documentation/SubmittingPatches file. First, you don’t want to submit any whitespace errors. Git provides an easy way to check for this – before you commit, run git diff --check , which identifies possible whitespace errors and lists them for you. Figure 57. Output of git diff -check . If you run that command before committing, you can tell if you’re about to commit whitespace issues that may annoy other developers. Next, try to make each commit a logically separate changeset. If you can, try to make your changes digestible – don’t code for a whole weekend on five different issues and then submit them all as one massive commit on Monday. Even if you don’t commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit. If some of the changes modify the same file, try to use git add --patch to partially stage files (covered in detail in Interactive Staging ). The project snapshot at the tip of the branch is identical whether you do one commit or five, as long as all the changes are added at some point, so try to make things easier on your fellow developers when they have to review your changes. This approach also makes it easier to pull out or revert one of the changesets if you need to later. Rewriting History describes a number of useful Git tricks for rewriting history and interactively staging files – use these tools to help craft a clean and understandable history before sending the work to someone else. The last thing to keep in mind is the commit message. Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior – this is a good guideline to follow. It’s also a good idea to use the imperative present tense in these messages. In other words, use commands. Instead of “I added tests for” or “Adding tests for,” use “Add tests for.” Here is a template originally written by Tim Pope: Short (50 chars or less) summary of changes More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, preceded by a single space, with blank lines in between, but conventions vary here If all your commit messages look like this, things will be a lot easier for you and the developers you work with. The Git project has well-formatted commit messages – try running git log --no-merges there to see what a nicely formatted project-commit history looks like. In the following examples, and throughout most of this book, for the sake of brevity this book doesn’t have nicely-formatted messages like this; instead, we use the -m option to git commit . Do as we say, not as we do. Private Small Team The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source – not accessible to the outside world. You and the other developers all have push access to the repository. In this environment, you can follow a workflow similar to what you might do when using Subversion or another centralized system. You still get the advantages of things like offline committing and vastly simpler branching and merging, but the workflow can be very similar; the main difference is that merges happen client-side rather than on the server at commit time. Let’s see what it might look like when two developers start to work together with a shared repository. The first developer, John, clones the repository, makes a change, and commits locally. (The protocol messages have been replaced with ... in these examples to shorten them somewhat.) # John's Machine $ git clone john@githost:simplegit.git Initialized empty Git repository in /home/john/simplegit/.git/ ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'removed invalid default value' [master 738ee87] removed invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) The second developer, Jessica, does the same thing – clones the repository and commits a change: # Jessica's Machine $ git clone jessica@githost:simplegit.git Initialized empty Git repository in /home/jessica/simplegit/.git/ ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Now, Jessica pushes her work up to the server: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master John tries to push his change up, too: # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' John isn’t allowed to push because Jessica has pushed in the meantime. This is especially important to understand if you’re used to Subversion, because you’ll notice that the two developers didn’t edit the same file. Although Subversion automatically does such a merge on the server if different files are edited, in Git you must merge the commits locally. John has to fetch Jessica’s changes and merge them in before he will be allowed to push: $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master At this point, John’s local repository looks something like this: Figure 58. John’s divergent history. John has a reference to the changes Jessica pushed up, but he has to merge them into his own work before he is allowed to push: $ git merge origin/master Merge made by recursive. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) The merge goes smoothly – John’s commit history now looks like this: Figure 59. John’s repository after merging origin/master . Now, John can test his code to make sure it still works properly, and then he can push his new merged work up to the server: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master Finally, John’s commit history looks like this: Figure 60. John’s history after pushing to the origin server. In the meantime, Jessica has been working on a topic branch. She’s created a topic branch called issue54 and done three commits on that branch. She hasn’t fetched John’s changes yet, so her commit history looks like this: Figure 61. Jessica’s topic branch. Jessica wants to sync up with John, so she fetches: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master That pulls down the work John has pushed up in the meantime. Jessica’s history now looks like this: Figure 62. Jessica’s history after fetching John’s changes. Jessica thinks her topic branch is ready, but she wants to know what she has to merge into her work so that she can push. She runs git log to find out: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 removed invalid default value The issue54..origin/master syntax is a log filter that asks Git to only show the list of commits that are on the latter branch (in this case origin/master ) that are not on the first branch (in this case issue54 ). We’ll go over this syntax in detail in Commit Ranges . For now, we can see from the output that there is a single commit that John has made that Jessica has not merged in. If she merges origin/master , that is the single commit that will modify her local work. Now, Jessica can merge her topic work into her master branch, merge John’s work ( origin/master ) into her master branch, and then push back to the server again. First, she switches back to her master branch to integrate all this work: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. She can merge either origin/master or issue54 first – they’re both upstream, so the order doesn’t matter. The end snapshot should be identical no matter which order she chooses; only the history will be slightly different. She chooses to merge in issue54 first: $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) No problems occur; as you can see it was a simple fast-forward. Now Jessica merges in John’s work ( origin/master ): $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Everything merges cleanly, and Jessica’s history looks like this: Figure 63. Jessica’s history after merging John’s changes. Now origin/master is reachable from Jessica’s master branch, so she should be able to successfully push (assuming John hasn’t pushed again in the meantime): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Each developer has committed a few times and merged each other’s work successfully. Figure 64. Jessica’s history after pushing all changes back to the server. That is one of the simplest workflows. You work for a while, generally in a topic branch, and merge into your master branch when it’s ready to be integrated. When you want to share that work, you merge it into your own master branch, then fetch and merge origin/master if it has changed, and finally push to the master branch on the server. The general sequence is something like this: Figure 65. General sequence of events for a simple multiple-developer Git workflow. Private Managed Team In this next scenario, you’ll look at contributor roles in a larger private group. You’ll learn how to work in an environment where small groups collaborate on features and then those team-based contributions are integrated by another party. Let’s say that John and Jessica are working together on one feature, while Jessica and Josie are working on a second. In this case, the company is using a type of integration-manager workflow where the work of the individual groups is integrated only by certain engineers, and the master branch of the main repo can be updated only by those engineers. In this scenario, all work is done in team-based branches and pulled together by the integrators later. Let’s follow Jessica’s workflow as she works on her two features, collaborating in parallel with two different developers in this environment. Assuming she already has her repository cloned, she decides to work on featureA first. She creates a new branch for the feature and does some work on it there: # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) At this point, she needs to share her work with John, so she pushes her featureA branch commits up to the server. Jessica doesn’t have push access to the master branch – only the integrators do – so she has to push to another branch in order to collaborate with John: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica e-mails John to tell him that she’s pushed some work into a branch named featureA and he can look at it now. While she waits for feedback from John, Jessica decides to start working on featureB with Josie. To begin, she starts a new feature branch, basing it off the server’s master branch: # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Now, Jessica makes a couple of commits on the featureB branch: $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Jessica’s repository looks like this: Figure 66. Jessica’s initial commit history. She’s ready to push up her work, but gets an e-mail from Josie that a branch with some initial work on it was already pushed to the server as featureBee . Jessica first needs to merge those changes in with her own before she can push to the server. She can then fetch Josie’s changes down with git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Jessica can now merge this into the work she did with git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) There is a bit of a problem – she needs to push the merged work in her featureB branch to the featureBee branch on the server. She can do so by specifying the local branch followed by a colon (:) followed by the remote branch to the git push command: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee This is called a refspec . See The Refspec for a more detailed discussion of Git refspecs and different things you can do with them. Also notice the -u flag; this is short for --set-upstream , which configures the branches for easier pushing and pulling later. Next, John e-mails Jessica to say he’s pushed some changes to the featureA branch and ask her to verify them. She runs a git fetch to pull down those changes: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Then, she can see what has been changed with git log : $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 Finally, she merges John’s work into her own featureA branch: $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Jessica wants to tweak something, so she commits again and then pushes this back up to the server: $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Jessica’s commit history now looks something like this: Figure 67. Jessica’s history after committing on a feature branch. Jessica, Josie, and John inform the integrators that the featureA and featureBee branches on the server are ready for integration into the mainline. After the integrators merge these branches into the mainline, a fetch will bring down the new merge commit, making the history look like this: Figure 68. Jessica’s history after merging both her topic branches. Many groups switch to Git because of this ability to have multiple teams working in parallel, merging the different lines of work late in the process. The ability of smaller subgroups of a team to collaborate via remote branches without necessarily having to involve or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 69. Basic sequence of this managed-team workflow. Forked Public Project Contributing to public projects is a bit different. Because you don’t have the permissions to directly update branches on the project, you have to get the work to the maintainers some other way. This first example describes contributing via forking on Git hosts that support easy forking. Many hosting sites support this (including GitHub, BitBucket, Google Code, repo.or.cz, and others), and many project maintainers expect this style of contribution. The next section deals with projects that prefer to accept contributed patches via e-mail. First, you’ll probably want to clone the main repository, create a topic branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone (url) $ cd project $ git checkout -b featureA # (work) $ git commit # (work) $ git commit Note You may want to use rebase -i to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review – see Rewriting History for more information about interactive rebasing. When your branch work is finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add in this new repository URL as a second remote, in this case named myfork : $ git remote add myfork (url) Then you need to push your work up to it. It’s easiest to push the topic branch you’re working on up to your repository, rather than merging into your master branch and pushing that up. The reason is that if the work isn’t accepted or is cherry picked, you don’t have to rewind your master branch. If the maintainers merge, rebase, or cherry-pick your work, you’ll eventually get it back via pulling from their repository anyhow: $ git push -u myfork featureA When your work has been pushed up to your fork, you need to notify the maintainer. This is often called a pull request, and you can either generate it via the website – GitHub has it’s own Pull Request mechanism that we’ll go over in GitHub – or you can run the git request-pull command and e-mail the output to the project maintainer manually. The request-pull command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and outputs a summary of all the changes you’re asking to be pulled in. For instance, if Jessica wants to send John a pull request, and she’s done two commits on the topic branch she just pushed up, she can run this: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: John Smith (1): added a new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) The output can be sent to the maintainer–it tells them where the work was branched from, summarizes the commits, and tells where to pull this work from. On a project for which you’re not the maintainer, it’s generally easier to have a branch like master always track origin/master and to do your work in topic branches that you can easily discard if they’re rejected. Having work themes isolated into topic branches also makes it easier for you to rebase your work if the tip of the main repository has moved in the meantime and your commits no longer apply cleanly. For example, if you want to submit a second topic of work to the project, don’t continue working on the topic branch you just pushed up – start over from the main repository’s master branch: $ git checkout -b featureB origin/master # (work) $ git commit $ git push myfork featureB # (email maintainer) $ git fetch origin Now, each of your topics is contained within a silo – similar to a patch queue – that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so: Figure 70. Initial commit history with featureB work. Let’s say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges. In this case, you can try to rebase that branch on top of origin/master , resolve the conflicts for the maintainer, and then resubmit your changes: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA This rewrites your history to now look like Commit history after featureA work. . Figure 71. Commit history after featureA work. Because you rebased the branch, you have to specify the -f to your push command in order to be able to replace the featureA branch on the server with a commit that isn’t a descendant of it. An alternative would be to push this new work to a different branch on the server (perhaps called featureAv2 ). Let’s look at one more possible scenario: the maintainer has looked at work in your second branch and likes the concept but would like you to change an implementation detail. You’ll also take this opportunity to move the work to be based off the project’s current master branch. You start a new branch based off the current origin/master branch, squash the featureB changes there, resolve any conflicts, make the implementation change, and then push that up as a new branch: $ git checkout -b featureBv2 origin/master $ git merge --no-commit --squash featureB # (change implementation) $ git commit $ git push myfork featureBv2 The --squash option takes all the work on the merged branch and squashes it into one non-merge commit on top of the branch you’re on. The --no-commit option tells Git not to automatically record a commit. This allows you to introduce all the changes from another branch and then make more changes before recording the new commit. Now you can send the maintainer a message that you’ve made the requested changes and they can find those changes in your featureBv2 branch. Figure 72. Commit history after featureBv2 work. Public Project over E-Mail Many projects have established procedures for accepting patches – you’ll need to check the specific rules for each project, because they will differ. Since there are several older, larger projects which accept patches via a developer mailing list, we’ll go over an example of that now. The workflow is similar to the previous use case – you create topic branches for each patch series you work on. The difference is how you submit them to the project. Instead of forking the project and pushing to your own writable version, you generate e-mail versions of each commit series and e-mail them to the developer mailing list: $ git checkout -b topicA # (work) $ git commit # (work) $ git commit Now you have two commits that you want to send to the mailing list. You use git format-patch to generate the mbox-formatted files that you can e-mail to the list – it turns each commit into an e-mail message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body. The nice thing about this is that applying a patch from an e-mail generated with format-patch preserves all the commit information properly. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch The format-patch command prints out the names of the patch files it creates. The -M switch tells Git to look for renames. The files end up looking like this: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 You can also edit these patch files to add more information for the e-mail list that you don’t want to show up in the commit message. If you add text between the --- line and the beginning of the patch (the diff --git line), then developers can read it; but applying the patch excludes it. To e-mail this to a mailing list, you can either paste the file into your e-mail program or send it via a command-line program. Pasting the text often causes formatting issues, especially with “smarter” clients that don’t preserve newlines and other whitespace appropriately. Luckily, Git provides a tool to help you send properly formatted patches via IMAP, which may be easier for you. We’ll demonstrate how to send a patch via Gmail, which happens to be the e-mail agent we know best; you can read detailed instructions for a number of mail programs at the end of the aforementioned Documentation/SubmittingPatches file in the Git source code. First, you need to set up the imap section in your ~/.gitconfig file. You can set each value separately with a series of git config commands, or you can add them manually, but in the end your config file should look something like this: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = p4ssw0rd port = 993 sslverify = false If your IMAP server doesn’t use SSL, the last two lines probably aren’t necessary, and the host value will be imap:// instead of imaps:// . When that is set up, you can use git send-email to place the patch series in the Drafts folder of the specified IMAP server: $ git send-email *.patch 0001-added-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Then, Git spits out a bunch of log information looking something like this for each patch you’re sending: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] added limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you’re sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off. Summary This section has covered a number of common workflows for dealing with several very different types of Git projects you’re likely to encounter, and introduced a couple of new tools to help you manage this process. Next, you’ll see how to work the other side of the coin: maintaining a Git project. You’ll learn how to be a benevolent dictator or integration manager. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:44 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.