[영어 아티클 읽기] 4 ways GitHub engineers use GitHub Copilot

https://github.blog/2024-04-09-4-ways-github-engineers-use-github-copilot/

4 ways GitHub engineers use GitHub Copilot

 

깃허브 블로그에 있는 영어 아티클을 읽었다!

아티클을 읽고 영어로 요약 작문을 몇 문장 해보려고 한다. 

작문한 문장은 chatGPT로 첨삭해서 다시 올릴 것이다! 

( 영어 공부를 위한 것이니 틀린게 있을 수 있습니다! 참고하여 주세용 )

 

<summing - up>

This article discusses the four ways GitHub engineers utilize GitHub Copilot - Copilot moments.

 

1. use Copilot for get comprehensive collection of significant dependencies for nearly all supported languages

2.Semi-automating repetitive tasks

3. Avoid getting side tracked

He didn't want his workflow disturbed by changing to chat mode. So he change the code to put propmt in the code with annotation. 

-> "He didn't want his workflow to be disrupted by switching to chat mode, so he adjusted the code to include comments with annotations."

4. Exploring and learning

 

 

<생소한 개념>

What is user’s project dependencies?

It is related with libraries. In Java if one class depend on other class, then it is hard to reuse the class. And sometimes dependencies make problems such as if the class depended by other class is gone the depending class also become error.

=> "In Java, if one class depends on another class, it can be difficult to reuse the dependent class. Sometimes, dependencies can cause issues; for example, if the class that another class depends on is removed, the dependent class will also encounter errors." (GPT)

 

What is machine-processable dependencies? (ask to ChatGPT)

 

• Package Management Files: Dependencies are commonly listed in specific files like package.json (Node.js), requirements.txt (Python), build.gradle (Java), etc. These files are designed to be machine-readable and typically include information about the exact versions of libraries or modules required by the project.
• Versioning: Dependencies often specify version ranges or specific versions that are compatible with the project. Tools can interpret these version specifications to automatically fetch and install the correct dependencies.
• Metadata: Package managers and build tools often rely on metadata associated with each dependency to determine compatibility, licensing, and other relevant information. This metadata is structured in a way that software tools can process efficiently.
• Dependency Resolution: Automated systems use algorithms to resolve dependencies, ensuring that all required libraries and modules are installed in compatible versions. This process involves understanding dependencies' relationships and constraints specified in configuration files.
• Integration with CI/CD Pipelines: Machine-processable dependencies are crucial for continuous integration and continuous deployment (CI/CD) pipelines. These pipelines automate the build, test, and deployment processes, relying on accurate dependency information to maintain consistency and reliability across different environments.

 

 

In summary, machine-processable dependencies refer to structured and standardized formats used by software tools and systems to automatically manage, fetch, and integrate external libraries and modules required by a software project. This automation streamlines development workflows and ensures consistency in software development and deployment processes.